On Wed, Sep 24, 2003 at 11:00:52PM -0600, Eric W. Biederman wrote:
Right. My only other guess is that some of the lba48 support my be interacting
in a strange way and causing problems. We always write the lba48 high
registers but we don't set them in the lba case. It should not cause a
hi ian,
The first is that I think the comments in the code may be a bit misleading
(apologies to the original author!)
AIUI the registers at 0x56 and 0x57 (and 0x5E and 0x5F as well) should be
set to the same value as 0x5D i.e. the DRAM ending address for your highest
populated bank of
On Wed, Sep 24, 2003 at 10:54:02PM -0600, Eric W. Biederman wrote:
I have seen IDE cables with a memory so I am not at all certain
about the floating detection.
I'm not sure about non-standard devices.
I believe this is what the commercial BIOS does.
Anyway FILO only touches the bus the user
* ron minnich [EMAIL PROTECTED] [030909 01:53]:
What happens is that linuxbios properly scans and enables bus 1, but the
linux that boots never scans bus 1 at all. So something is not quite set
up right. More as I find it.
I'm still having this problem on the Solo. Is there any fix
On Thu, 25 Sep 2003, Ian Smith wrote:
Blows a hole in my theory about the 128MB being detected
sorry, but those registers you are mentioning have *zero* impact on size
detection. That's not what's going on here. Size detect is via SPD.
We wrote a lot of that code here 3 years ago, and it
Hi Ron,
The right thing to do here is cut to freebios2 ASAP and write all this in
C. It's just too hard in assembly.
Is there any platform has been ported to freebios2 besides AMD64? Any
porting guide for that? Is it as easy as running buildtarget to generate
the build directory?
-Andrew
* Andrew Ip [EMAIL PROTECTED] [030925 16:03]:
The right thing to do here is cut to freebios2 ASAP and write all this in
C. It's just too hard in assembly.
Is there any platform has been ported to freebios2 besides AMD64? Any
Some PPC machines are supported as well.
porting guide for
Let's just start. Andrew, I will try to populate a skeleton epia directory
in freebios2, and we can start filling it in.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
Eric W. Biederman wrote:
I was going to force it to use ide_read_sector_chs but did not have time.
I switched to using my CF drive and it worked fine, so I don't think it was
cockpit trouble.
Right. My only other guess is that some of the lba48 support my be interacting
in a strange way and
I'm putting together an EPIA tree in V2. Give me a couple days.
If this works it's definitely what we want to do. It should work.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
ron minnich [EMAIL PROTECTED] writes:
I find this in the arima mainboard config:
## ROM_SIZE is the size of boot ROM that this board will use.
option ROM_SIZE = 524288
This is the wrong place. ROM_SIZE should always be in the target config
file, not the mainboard config file.
I've added a few things for epia.
epia folks please look in freebios2 at
src/northbridge/via/vt8601 (not done yet)
src/southbridge/via/vt8231
the big thing to look at in the southbridge is how it is set up. The
previous code was really out of touch w.r.t. the way you're supposed to do
in arima/hdama/Config.lb
##
## Clean up the motherboard id strings
##
option MAINBOARD_PART_NUMBER=HDAMA
option MAINBOARD_VENDOR=ARIMA
OK, the config tool will create this by default:
MAINBOARD_PART_NUMBER=hdama
MAINBOARD_VENDOR=arima
why do we need to put this type of thing in the mainboard
On 25 Sep 2003, Eric W. Biederman wrote:
If no objections, I am going to remove the default setting in Options.lb,
make the mainboard ROM_SIZE settings defaults, so I can continue to set
them in the target config files.
That sounds like a good path forward.
committed.
Also, I
Is this like a secret club where only members can contribute or view the
actual code talked about? How come no one else has any trouble getting hold
of the source or latest CVS, how come everyone else can check in code and
presumably check out latest with no trouble? IT IS BROKEN!
you're not missing anything. Sourceforge is sucking big time.
if it is not fixed soon, I'll be moving my projects.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Thu, Sep 25, 2003 at 07:40:06AM -0600, ron minnich wrote:
On Thu, 25 Sep 2003, Ian Smith wrote:
Blows a hole in my theory about the 128MB being detected
sorry, but those registers you are mentioning have *zero* impact on size
detection. That's not what's going on here. Size detect
On Fri, 26 Sep 2003, SONE Takeshi wrote:
EPIA and EPIA-M are two totally different boards (different chipsets,
etc).
stupid ofme. I got mixed up because so many of the registers are the same.
So, please open a epia-m directory, instead of epia, in the freebios2
tree.
I'm going to do both.
The config tool has been changed to allow 'default' statements in the
mainboard file.
Now, you can have
default ROM_SIZE 512*1024
in the mainboard file, and over-ride that with (e.g.)
option ROM_SIZE=1024*1024
in the target file.
I've tested this and it works fine; it's now committed.
No need, since it's done automatically now.
Greg
At 11:26 AM -0600 25/9/03, ron minnich wrote:
in arima/hdama/Config.lb
##
## Clean up the motherboard id strings
##
option MAINBOARD_PART_NUMBER=HDAMA
option MAINBOARD_VENDOR=ARIMA
OK, the config tool will create this by default:
Then where can the config tool got that info to produce
MAINBOARD_PART_NUMBER=hdama
MAINBOARD_VENDOR=arima
YH
--
: Greg Watson [mailto:[EMAIL PROTECTED]
: 2003925 16:53
: ron minnich; [EMAIL PROTECTED]
: Re: why are we still doing this?
No need, since it's done automatically now.
Greg
Hello from Gregg C Levine
Well, according to the joker in charge of Source Forge, as a whole,
CVS was supposed to be moved to a larger, and bigger box, starting
sometime this week. Ron, here's a suggestion, keep collecting these
complaints, make a note as to the date, and time of each complaint.
Yeah, but it's free. It's hard to complain too hard.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Thu, 25 Sep 2003, YhLu wrote:
Then where can the config tool got that info to produce
MAINBOARD_PART_NUMBER=hdama
MAINBOARD_VENDOR=arima
The config tool produces it automatically from the name of the mainboard.
In other words, when you say:
mainboard arima/hdama
The config tools
ron minnich [EMAIL PROTECTED] writes:
in arima/hdama/Config.lb
##
## Clean up the motherboard id strings
##
option MAINBOARD_PART_NUMBER=HDAMA
option MAINBOARD_VENDOR=ARIMA
OK, the config tool will create this by default:
MAINBOARD_PART_NUMBER=hdama
MAINBOARD_VENDOR=arima
why
I'm putting the pieces together but this will go lots faster with help.
If somebody can look at
freebios2/src/via/southbridge/vt8231/vt8231_early_smbus.c and send me
fixes for the actual correct code, that will save a lot of time.
If I can toss these kinds of tasks out and get help, we
OK, if you
cd targets
./buildtarget epia/via
-bash-2.05b$ cd targets/via/epia/epia/
-bash-2.05b$ make
if (cd fallback; \
make linuxbios.rom)\
then true; else exit 1; fi;
make[1]: Entering directory
`/home/rminnich/src/bios/freebios2/targets/via/epia/epia/fallback'
./romcc -O ./auto.E
27 matches
Mail list logo
