Hi,
it seems we finally have achieved our goal of active vendor
participation, that is, we don't have to beg for data sheets anymore,
but vendors come to us with code and ask how they can help us.
That's really great!
Here's a preliminary non-exhaustive list of code areas and involved
vendors (additions/corrections welcome):
Processors:
- AMD contributes code
North-/Southbridges:
- AMD contributes code
- SiS contributes code
Super I/Os:
- Winbond has offered help
Flash chips:
- Macronix …
[View More]has offered help
The "fast feedback, fast commit" way of dealing with code contributions
has been very successful since we practice it, so I'd like to continue
that way.
That leaves us with the task to formalize (or at least establish
guidelines for) contacts with vendors who have offered help.
Suggestions:
* Single point of contact which will not bounce/reject mail and
guarantees speedy and/or confidential response.
* E-mail address should be @linuxbios.org and forward to a unmoderated,
spam-filtered, non-public list.
* Once somebody of us picks up the vendor contact, he will continue with
it or delegate explicitly.
* Do we want to give vendors a telephone number for further inquiries?
* Do we want to keep a list of the locations where we live/work (no
precise address, only area)?
Reasons why I raised the last two points: I have gotten inquiries from a
vendor who would like to meet us face-to-face or at least organize a
conference call to better understand our mission and how to help us.
That's great and I'd like to tell them: "Yes, we care, we can set up
something."
Regards,
Carl-Daniel
[View Less]
Hi all,
I've recently checked out and built revision 2977 of flashrom in order
to apply a simple BIOS configuration change to approx 200 embedded Linux
devices.
Unfortunately although flashrom is able to read the contents of the BIOS
flash, writes fail to take (verification fails).
The system basics are as follows:
IEI NanoLX Board (AMD LX800 + CS5536 + Winbond W83627EHG)
http://www.ieiworld.com/en/product_IPC.asp?model=NANO-LX
Linux Kernel Version 2.6.20
Flash part identified by flashrom …
[View More]as Pm49FL004 at physical
address 0xfff80000 (512 KB)
I see from the source code that the CS5536 chipset is directly supported
and that the code attempts to remove the write protection via MSR
0x1808. This all looks good and yet the writes fail to take. I assume
therefore that this board is using some GPIOs to disable writes to the
BIOS flash?
Does it sound likely that GPIOs are causing the write problem that I am
seeing? Does anyone know how I might go about figuring out which GPIOs
to look at?
Any help would be very appreciated.
Best regards,
Alan Alexander mailto:alan@icerasemi.com
Icera Inc, 2520 The Quadrant, Aztec west, Bristol BS32 4AQ, UK
Tel. +44 (0)1454 284805
--
******************************************************************************************
This e-mail (including any attachments) is intended only for the recipient(s)
named above. It may contain confidential or privileged information and should
not be read, copied or otherwise used by any other person. If you are not a
named recipient, please contact the sender by telephone (+44-1454-284800)
and destroy the original message.
Any statement and/or opinion not related to this company's business and
expressed in this message is that of the author and does not necessarily
reflect those of Icera. This company does not take any responsibility
for the views of the author in any matter not related to the
company's objective.
******************************************************************************************
[View Less]
Hi, all,
Another questiong about IRQ: The interrupt line register in PCI configurationn space also contains an IRQ number, for example, my ethernet card is IRQ 10, the IRQ number is the interrupter vector in x86 or the physical signal in APIC or PIC?
best regards
flb
_________________________________________________________________
Windows Live Spaces 中最年轻的成员!
http://miaomiaogarden2007.spaces.live.com/