Ticket #46 (new enhancement)

Opened 8 years ago

Last modified 6 years ago

Eliminate dependency on licensed code in Marvell firmware.

Reported by: jg Owned by: jg
Priority: low Milestone: Opportunity
Component: hardware Version:
Keywords: Cc: mbletsas@…, olpc@…, shirishag75@…, mtd, grantbow
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description (last modified by cjb) (diff)

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

  Changed 8 years ago by marcelo

Requires documentation/cooperation from Marvell about the internal workings of the chip.

Are they willing to go that route?

follow-up: ↓ 10   Changed 8 years ago by 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.

Cheers! MarkF

P.S. This should actually be assigned to mbletsas@…, but he doesn't have a Trac account yet.

follow-up: ↓ 6   Changed 8 years ago by krstic

  • priority changed from normal to wishlist
  • cc m@… added
  • milestone set to rev2 final

  Changed 8 years ago by cjb

  • milestone changed from Gen2 to Opportunity

  Changed 8 years ago by mfoster

  • cc mbletsas@… added; m@… removed
  • owner changed from mfoster to jg

Improper assignment. This is mbletsas' area of responsibility. Sorry!

in reply to: ↑ 3   Changed 8 years ago by RafaelOrtiz

  • description modified (diff)

Replying to krstic:

  Changed 8 years ago by cjb

  • 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.

  Changed 8 years ago by AlbertCahalan

I'd like to give it a try. Please send documentation.

  Changed 7 years ago by palfrey

  • 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.

in reply to: ↑ 2   Changed 7 years ago by bobkeyes

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.

  Changed 7 years ago by Mokurai

We're going to have a go at this. See  http://wiki.laptop.org/go/Marvell_microkernel for orientation.

  Changed 6 years ago by shirish

  • cc shirishag75@… added
  • next_action set to never set

  Changed 6 years ago by shirish

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.

  Changed 6 years ago by mtd

  • cc mtd added

  Changed 6 years ago by grantbow

  • cc grantbow added
Note: See TracTickets for help on using tickets.