Ronak Chokshi wrote:
The OLPC manufacturing data that I was talking about is in the same
FLASH that contains the system BIOS. Is that the sort of "external
flash memory" that you recommend?
Yes.
Ronak
Given the choice between putting this on the onboard SPI flash and
putting it as a config option for the driver, I would rather it be part
of the driver. It's just more convenient for us and the other option
just adds another level of pain for per-country flashing.
--Chris
-----Original Message-----
From: Mitch Bradley [mailto:[EMAIL PROTECTED]
Sent: Monday, October 02, 2006 4:26 PM
To: Ronak Chokshi
Cc: Dan Williams; [email protected]; Michail Bletsas; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: Marvell regulatory domain info storage?
Ronak Chokshi wrote:
- Burning the region code in the manufacturing data of the
EEPROM is an option but a slightly difficult one. A better suggestion
would be maintain this information on an external flash memory and
have the driver read this information from the flash. This is what we
have suggested to most of our customers also.
The OLPC manufacturing data that I was talking about is in the same
FLASH that contains the system BIOS. Is that the sort of "external
flash memory" that you recommend?
We were not intending to change the EEPROM that is attached to the
Marvell wireless device on a per-county basis.
This also has an added advantage that it keeps the WLAN module the
same for all the laptops going in several countries.
Yes, that is our intention.
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
