DELETED


If anyone notices the blog going spaz in the next hour or so, it's because I'm tweaking the CSS and Wordpress is a steaming hat full of arse. FYI.
ohhhh... so that's why the pandora/wordpress logo was gone :unsure:
i thought my adblock was going crazy :lol:
 
Last edited by a moderator:
Gasp! Where has mali been? The unofficial hunter of deep forum news! mali has been missing in action for quite some time. There should be an announcement to find him!!!
He switched to lurk mode and relied on the Community Blog for info.
Many thanks to the Blog Guys, especially Gruso :)
 
Last edited by a moderator:
Last edited by a moderator:
ED also posted a follow-up on the blog about the TV-Out cable:

QUOTE
Geez, I just got some up-to-date news I don't want to hold back.

The TV Out cable design is also finished and a prototype can be produced within five days. Nice :D
 
Maybe not dense enough to get a blog entry, but nonetheless something that shouldn't get burried, so I'll just post it here.
As for WebOS, we already share a great deal. WebOS is built using Open Embedded (just like the Pandora) and while Palm have noted that there GUI elements are closed you can be very sure that any cool stuff they have done with open source bits will get fed up into mainline Open Embedded and from there trickle down to the Pandora (both directly and via the Angstrom distro).

In short: Android basically runs on Pandora, WebOS apps will most likely run on Pandora, too.
It could be interesting to squeeze some more info out of DJWillis about this. Android is a nice topic to fetch some headlines ;)
 
Last edited by a moderator:
QUOTE
Maybe not dense enough to get a blog entry, but nonetheless something that shouldn't get burried, so I'll just post it here.
Agreed on both points. :) Definitely an interesting bit of info, could be handy to refer to later.

We did put a blog post up when Android was ported to Beagleboard, but (surprisingly) no one even commented. :( Android on a Pandora screen will make for a nice story when we have pics though.
 
ED posts new info about the wifi driver.

QUOTE ("Official Blog")
Hiya, it's EvilDragon again.

I got some more fresh news, and those are not about delaying or anything like that.

As you have all read, the only driver problem is WiFi. To put things short (and as they are pretty complicated), here is what was our problem:

There's a closed-source driver available for the WiFi chip, but we didn't at all want to use it (hey, we're OPENPandora, not ClosedPandora). Then we found an OpenSource project for that WiFi chip - we used it and it worked well at the beginning (you might remember some WiFi testing videos).
But that driver was poorly coded - and it did have more and more problems. We can't even get to work it anymore with the latest Angström image, only with our testing rootfs (which is good, as we do know that the hardware is fine.

Well, DJWillis wanted to take on the WiFi task - and it's already looking really good. He found another driver which should work way better - and it already compiled with our latest kernel.

So basically, that WiFi issue MIGHT be solved faster than we thought. There's still a lot of work needed, but this has been a HUGE progress.

I'll keep you informed.


http://openpandora.org/blog.php

Edit: Quoted blog. :)
 
Good news :)
I remember DJWillis posting in the Beagleboard IRC about using G1's driver long ago. I should check the log, there could be new info.
Edit:
DJWillis explains the driver situation:
I don’t see why they couldn’t have just included the closed source WIFI drier in the firmware until the open source one was ready; add it the first update.
I’ll elaborate sometime on that but lets just say that is not a viable option for many reasons.



Anyway, we actually have 2 open source options so I’ll give people a little background.

One is the TI WiLink 4 based ‘partial’ driver that was opened as part of the Google Android G1 release.

This driver is unfortunately a mess and really has no place in a modern system (ancient design architecture, lots of semi-bespoke shims, some really nasty bugs etc.).

We can use this driver if you don’t mind setting it up from one clunky user space app that crashes a lot and lacks solid support for things like WEP/WPA etc. – Really this driver is only of use for hardware validation not real use from users. Even after I hacked in Wireless Extensions support (yep, the driver is THAT old) it’s still not a driver I would want to use (sorry but I hate lots of nasty random mem leaks and errors).



The next open option is the WL12xx driver written by Kalle Valo of Nokia. This is a nice modern driver (MAC80211) and is already in Wireless-Testing (as of a few days ago) and on its way to mainline.

This driver was SPI only but a gent by the name of Bob Copeland added the start of SDIO support and we are working off that base to bring the driver up on the Pandora so we have a nice solid mainline driver to use that is actively developed, supports the Pandora out of the gate, and is easy to maintain.

As of now I have the WL2151 firmware loading on the Pandora with the new driver and lots of nice signs of life but the work is a little way away from passing traffic ;) (the Linux SDIO stack is causing me pain).

Not sure if that counts as an update ;) .

but I have been getting some helpful advice on that front so the plan is to sink a few hours into that over the weekend. Started to push a few simple patches upstream for things like chip ID's so with any luck by the time the driver hits mainline the Pandora should 'just work' if I can nail all the SDIO bits.
Once I get things settled (hopefully) I want to have a play with trying to get hostapd going as I have some funky uses for a mobile access point in mind ;).

If anyone wants patches (or is familiar with the kernels SDIO stack) drop me a bell.

John
 
Last edited by a moderator:
Back
Top