Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Opened 15 years ago
Last modified 12 years ago
#46 new enhancement
Eliminate dependency on licensed code in Marvell firmware.
| Reported by: | Jim Gettys | Owned by: | Jim Gettys |
|---|---|---|---|
| Priority: | low | Milestone: | Opportunity |
| Component: | hardware | Version: | |
| Keywords: | Cc: | mbletsas@…, olpc@…, shirishag75@…, mtd, Grant Bowman | |
| Blocked By: | Blocking: | ||
| Deployments affected: | Action Needed: | never set | |
| Verified: | no |
Description (last modified by )
We are using a Marvell Wireless chip; it has an ARM 9 processor and something like 96K of RAM.
Marvell licensed a proprietary microkernel as a framework for developing their firmware for the chip.
Since Marvell does not own this code, it is not theirs to give away, though much/most of the code now in the firmware is not encumbered. A suitably motivated person could take the OLPC code and retarget it for some other small embedded operating system (e.g. TinyOS, maybe), and then the firmware could itself be open source.
This would be very nice indeed, but OLPC itself does not have the resources to put into this. If someone volunteers, we can make the code available for porting to a free system.
Change History (16)
comment:1 Changed 14 years ago by
comment:2 follow-up: 10 Changed 14 years ago by
Hi, Marcelo!
Actually, we'll have no problem getting started under NDA. Once that's in place for the core developers, we'd then move to an alternate O.S., and we could then be truly Open Source.
Cheers! MarkF
P.S. This should actually be assigned to mbletsas@…, but he doesn't have a Trac account yet.
comment:3 follow-up: 6 Changed 14 years ago by
| Cc: | m@… added |
|---|---|
| Milestone: | → rev2 final |
| Priority: | normal → wishlist |
comment:4 Changed 14 years ago by
| Milestone: | Gen2 → Opportunity |
|---|
comment:5 Changed 14 years ago by
| Cc: | mbletsas@… added; m@… removed |
|---|---|
| Owner: | changed from Mark J. Foster to Jim Gettys |
Improper assignment. This is mbletsas' area of responsibility. Sorry!
comment:7 Changed 14 years ago by
| Description: | modified (diff) |
|---|
Rafael Ortiz says:
Is there any posibility to use a different chip with O.S Firmware in the future...?
The Marvell chip has very specific features that are essential to us -- stores its routing table in RAM, can forward packets through the mesh at low power while the main CPU is off, etc. We could only consider using a replacement if one existed with these features.
comment:9 Changed 14 years ago by
| Cc: | olpc@… added |
|---|---|
| Verified: | unset |
Add me to CC. I have experience with building radio-interfacing code in TinyOS for a couple of platforms, and I've be interested in seeing what could be done here.
comment:10 Changed 14 years ago by
Replying to mfoster:
Hi, Marcelo!
Actually, we'll have no problem getting started under NDA. Once that's in place for the core developers, we'd then move to an alternate O.S., and we could then be truly Open Source.
I'd be interested in helping out the porting to tinyos or similar, so the firmware could become open source. People involved: please send me some email about how to get started.
comment:11 Changed 13 years ago by
comment:12 Changed 13 years ago by
We're going to have a go at this. See http://wiki.laptop.org/go/Marvell_microkernel for orientation.
comment:13 Changed 13 years ago by
| Action Needed: | → never set |
|---|---|
| Cc: | shirishag75@… added |
comment:14 Changed 13 years ago by
sorry don't know if the action should be to never set or not. Just wanted to add myself to the bug, please revert if I did something by mistake.
comment:15 Changed 13 years ago by
| Cc: | mtd added |
|---|
comment:16 Changed 12 years ago by
| Cc: | Grant Bowman added |
|---|
Requires documentation/cooperation from Marvell about the internal workings of the chip.
Are they willing to go that route?