>
> Along the same lines, has anyone tried using different size SST chips?
I
> tried to duplicate the 256KB bios by putting it in a 512KB chip (SST
> 28SF040A vs 39SF020A). This didn't seem to work (no beep or video but
> didn't try port 80 parallel card yet). Perhaps someone knows if this
> should work. Can someone recommend a good place to get a handful of
SST
> 39SF02A PLCC chips for these experiments?
Look for the device data sheet on the SST Web site. If the device is
pin compatible, it should work. Usually pin compatible devices have the
same first 4 characters and the last 4 describe the capacity.
Steve
Does the current Linux Bios support use of disk passwords
at bootup as defined in the ATA specs?
Thanks,
Dave Feustel
--
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE,
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
That is right...that is different to any other E7500 MB.
YH
-----Original Message-----
From: linuxbios-bounces(a)openbios.org
[mailto:linuxbios-bounces@openbios.org] On Behalf Of Steven J. Magnani
Sent: Wednesday, September 14, 2005 11:06 AM
To: linuxbios(a)openbios.org
Subject: [LinuxBIOS] APIC IDs for Tyan s2735
YhLu -
Can you check the mptable for the S2735? If I'm reading it correctly,
APIC ID 8 is being used for the ICH, but it seems from the southbridge
code that the ICH is hard-coded to 2.
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
--
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
It's good to have spd.h there.
But the name should be changed for support DDR2...etc.
YH
-----Original Message-----
From: linuxbios-bounces(a)openbios.org
[mailto:linuxbios-bounces@openbios.org] On Behalf Of Steven J. Magnani
Sent: Tuesday, September 13, 2005 8:08 AM
To: linuxbios(a)openbios.org
Subject: [LinuxBIOS] E7501 Raminit rewrite
This one ends up being a little more than a "patch".
I ended up reorganizing the E7501 raminit code so I could follow it, and
fixed some bugs along the way.
Significant logical changes:
* Added support for "fast" (64-clock) refresh
* Added code to support remap window for 3 - 4 GB systems
* Fixed premature configuration of true row boundaries that resulted in
some sections of DRAM not receiving JEDEC commands (see
http://openbios.org/pipermail/linuxbios/2005-June/011752.html).
* Redefined RCOMP_MMIO so that RCOMP registers can be configured on
systems where A20M# is asserted.
* Disabled subsystem (vendor) ID configuration
* #ifdef'd out suspicious looking code (see
http://openbios.org/pipermail/linuxbios/2005-June/011759.html)
* Added optional run-time checking of dual-channel compatibility of
installed DIMMs
* Move JEDEC SPD and SDRAM definitions into reusable #include files
Probably, the rewritten code should be reviewed as if it were new. My
hope is that it is now easy enough to follow that this shouldn't be too
bad.
The original code is, of course, in Subversion. Since I reordered the
functions as part of the rewrite, a 'diff' of of the new code against
the original won't tell you much. I've attached a reordered copy of the
Subversion code that won't compile, but should be a little easier to
diff against the new code so you can see what's changed.
I will hold off on committing this for awhile to give people time to
look at it. I know that radical changes are a pain to review, but IMHO
the improvement in maintainability is significant.
New files that are part of this 'patch', but not included here (I
committed these to Subversion):
src/include/spd.h
src/include/sdram_mode.h
src/include/northbridge/intel/e7501/e7501.h
Thanks,
Steve
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
YhLu -
Can you check the mptable for the S2735? If I'm reading it correctly,
APIC ID 8 is being used for the ICH, but it seems from the southbridge
code that the ICH is hard-coded to 2.
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
Hey all,
I've been making some modifications to the ck804 early smbus code and i'm
noticin that romcc appears to be chewing seemingly forever.
Any ideas on how to diagnose this?
Hi,
We are working on the agenda for LinuxBIOS summit. Here is a draft
version. Please give us any suggestion and help you have.
We categorized the attendance into three parties, the vendors, the users
and the developers. We hope the three parties can each describe their
past experience, outstanding problems and future directions such that
these three parties can help each other.
The first day will be focus on current status report. We are going to
have
Oct. 11
Vendor Presentation
1. Richard Bruner from AMD will talk about
AMD's plan on LinuxBIOS and their roadmap
for their products.
2. LNXI will give us their experience on
integrating LinuxBIOS in their cluster
products.
3. Terra soft will give us their plan of
using LinuxBIOS in their PPC 970 products.
User Experience
Users from Sandia and Los Alamos will talk on
their experience of using LinuxBIOS in clusters.
Developer Status Report
Developers will give presentations and hands-on
demo of recent development. Topics includes:
1. Dual Core support for AMD K8
2. Cache As Ram support for Intel and
AMD processors.
3. Integrating VGA BIOS support in your
LinuxBIOS.
On the second day we will focus on making LinuxBIOS more friendly for
people of the three parties:
Oct. 12
User Friendly
1. User Interface: What kind of default payload
and/or user interface are we going to use?
Do we want it to be command line or menu
style?
2. User's Manual.
Developer Friendly
1. KConfig: Josaih England will show us his
work on using KConfig to replace the current
config tool.
2. Development Model: What is the svn commit
and release process?
3. Device Object Model: People still complain
about the complexity of the current device
model. Can we make it easier to work with?
What is the impact of a new config too like
#1 on the device model? How are we going to
generate PIRQ/ACPI etc. tables?
4. Programmer's Manual.
Vendor Friendly
1. We need to discuss the possibility of
signing N-party NDA with vendors for
their unreleased products.
2. How can we ensure 3rd party that our code
is clean and free of legal trouble?
3. Binary blob and EFI/Tiano Interface. How
are we going to play nice with Intel?
Hackathon
If anyone get inspired during the discussion,
start implement your idea immediately!!
On the third day we will look forward further into the future:
Oct. 13
Crazy Ideas
1. FreeFI: Possible name change and official
FSF sponsorship.
2. LinuxBIOS as Linux: Ron just doesn't give up
his old LinuxBIOS==Linux idea. He will show
how he is recycling it.
Homework Assignment
Hey, you had a good time. It is time to do your
homework now.
--
Li-Ta Lo <ollie(a)lanl.gov>
Los Alamos National Lab
Hi,
While we are working on the agenda of LinuxBIOS summit, we found
that we desperately need speakers from embedded device world.
Current we have no speaker who can stand for them. We would like
to hear from people who is currently deploying or trying to
deploying LinuxBIOS in their products. What problems did you
encounter when using LinuxBIOS? What kind of support do you need
from vendors and the developer community? Could you give us a big
picture of where and how many LinuxBIOS embedded systems you have
deployed out there?
People complained about that LinuxBIOS development was too slanted
to cluster application. Now it is time for people to hear from you!!!
So please, come up and speak!!!
--
Li-Ta Lo <ollie(a)lanl.gov>
Los Alamos National Lab