[Trac #46] Eliminate dependency on licensed code in Marvell firmware.

[Zarro Boogs per Child]

#46: Eliminate dependency on licensed code in Marvell firmware.
-------------------------+--------------------------------------------------
 Reporter:  jg           |        Owner:  jg         
     Type:  enhancement  |       Status:  new        
 Priority:  low          |    Milestone:  Opportunity
Component:  hardware     |   Resolution:             
 Keywords:               |  
-------------------------+--------------------------------------------------
Old description:

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

New description:

 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.

 Is there any posibility to use a different chip with O.S Firmware in the
 future...?

Comment (by RafaelOrtiz):

 Replying to [comment:3 krstic]:

-- 
Ticket URL: <http://dev.laptop.org/ticket/46#comment:6>
One Laptop Per Child <http://laptop.org/>