Archive for the ‘Ångström’ Category

SDE for Archos generation 8 devices released!

Wednesday, December 15th, 2010

Here it is:

http://www.archos.com/support/support_tech/updates.html (scroll down to the bottom, click ‘Show’, scroll again, click first button, acknowledge, download)

I haven’t tried it yet, but read on that page that it comes with a nice dual-boot menu out of the box! Let’s get it on and run some fun things on those new devices. The scope is all generation 8 Archos Internet Tablets: 28, 32, 43, 70 and 101!

Let’s discuss things on the openAOS-dev mailing list.

Cheers

Thomas

PS: Yes there should have been more/other blog posts, but personally I have a new job and far less time for openAOS than I’d like to at the moment. :-(
Although my new employer (Tieto Finland) is very supportive of open-source involvement, so in the future things should look better. :-)

Flash 10.1 anyone?

Tuesday, September 28th, 2010

This just in: There is an Adobe Flash 10.1 binary by TI to showcase flash on Cortex A8.

Who’s going to be the first to send us a video of Flash working in Firefox or Fennec under Ångström? Or someone could even try if replacing the plugin of the original opera browser would work.

Note: This is most likely not going to work on gen6. Supposedly needs Alsa while gen6 was OSS, also those units are quite RAM-limited.

An interim fix for booting Android and Ångström

Wednesday, September 15th, 2010

Bubu worked out how to tweak the kernel with fbset to do what we want.

A known working snapshot is here:

http://www.openaos.org/wp-upload/gen7/2010-09-15/

You’ll most likely only need the zImage and initramfs.

He added an temporary extension to the menu.lst structure. If you add ‘|1′ then fbset will set the framebuffer like in the original SDE kernel (e.g. for Ångström). If you add ‘|0′ then it will be set like for the Archos firmware and FroYo. In addition it tries to guess the right defaults: Everything gets the old 24 bit framebuffer unless it is: Archos firmware or the menu entry name contains ‘android’ or ‘froyo’, then it is set to the new mode.

Example for an android froyo override:
MyDroid|/dev/sda1|/rootfs.img|/init|0

Example for an linux image using SDE framebuffer override:
MyLinux|/dev/sda1|/rootfs.img|/sbin/init|1

This is a temporary hack though. We will rework the menu.lst structure to be more flexible in terms of options.

Archos releases updated GPL sources for gen7 devices

Thursday, August 5th, 2010

The sources released today contain kernel source for the 2.0.x line of Archos firmware. Especially the SGX/EGL kernel module sources are included which will be important for our FroYo and MeeGo endeavors.

We will soon start to sync the openAOS kernel to those sources.

Thanks Archos!

Should we start a feature-bounty programme?

Wednesday, August 4th, 2010

A thought that partly springs from necessity. I was thinking it might be nice to start a feature-bounty programme.

How would that work? Users that want a special feature implemented within the openAOS ecosystem would pledge to pay some amount of money or would put some amount of money into a deposit/escrow. Then if someone implements this feature the person would receive this amount. People could also pool their money to make it more attractive to implement a feature.

Why the idea? Hackers are often selfish people. Most of the time they implement things they need for themselves or that give them personal pleasure for tackling them. This may not be what non-programmer users would like to have as new features. Also a feature might be nice but only useful for very few people or not useful for the people potentially implementing it.

So what would be the benefits?

  • Features with popular demand would be implemented faster
  • People who want features that might not be popular could raise the chance of those being implemented
  • Features that may be harder to implement but more desirable than  others would get implemented faster
  • Faster development due to the monetary incentive
  • Developers may feel more rewarded for their work

I guess I should expand on the last one: the openAOS project has been around for more than half a year now, the openPMA project for much longer. We have done pretty nice things on many generations of Archos products. Many people have downloaded our alternative firmwares and our Linux builds. We spent weeks or months developing hacks, programs or just analyzing Archos hardware and software. But what did we get in return? A few people said ‘thanks’ or ‘great job’, but the majority of voices and feeback was “this doesn’t work!” or “But I want this [totally uncommon] feature, why didn’t you think of implementing it!” or other not very encouraging things.

We’d like to feel more appreciated!

And I mean it, if you can’t donate, but like what we did, just say ‘thanks’ it makes a day so much nicer! People of the ArchosFans forum, I’m looking at you! People with an genuine FOSS background already do. But back to the topic. I think – although not the ultimate solution – it would help both sides if there would be some transfer of monetary units involved. The users would get a feeling that TANSTAFL and the people working to make openAOS better could buy themselves a beer after a hard weekend of coding.

How is this different from commercial software you may ask or you might say that I’m trying to commercialize openAOS. Far from this, very very very far. Why? If a bounty is claimed a new feature is made available not only to the person who paid for it but to everyone who would like to use it, also the source code will be open – there is a reason this is called openAOS!

Thoughts? Critique? Rants? Praise? Flaming?- The comment section is open!

Thomas, your friendly neighbourhood Archdruid