On 8 Sep 2003, Eric W. Biederman wrote:
> Correct. It is a little better on the HDAMA. But currently there are
> some options that don't seem to work properly when I move them in closer.
yes, I've seen this too, not had time to fix it. Clearly, some things
should move into the mainboard file.
never flash the original bios. never.
try digikey or jameco for onesy-twosy orders. But the'll end up costing
more like $10 overall.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
linux is no longer seeing many of the pci devices. I'm going to take a
look, didn't see any obvious reason for this, but ...
This bit me as the IRQ router is no longer there.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.or
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.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org
I would love to see this happen, the only problem will be the lcd control
I think.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 9 Sep 2003, Niki Waibel wrote:
> is it necessary to do some unlocking before reading/writing
> to the bios area of the epia-m (vt8235)?
bash-2.05b$ more ~/src/bios/freebios/src/mainboard/via/epia/README
To enable flash write,
$ setpci -s 0:11.0 40.b=54
-Andrew
_
On Tue, 9 Sep 2003 [EMAIL PROTECTED] wrote:
> Hm - I haven't quite got your idea of scale, Ron. Is that "problem" a
> "slight inconvenience" or "several months and NDA'd docs"? :)
I wish I knew.
>
> I have seen various traffic go past about video BIOS, and noted how Adam
> and Adam dealt with
the 8111 is being put on pci bus 1, but Linux never sees it.
I'm not totally clear yet on why this is happening, but I've got to work
on a different problem with this board, so if anyone has any suggestions
I'll try them out later.
thanks
ron
___
On 9 Sep 2003, Eric W. Biederman wrote:
> Hmm. I will have to sync up with you. Are you certain the pirq table
> refers to a device on bus 1?
It does. The issue is that Linux does not enumerate any devices on Bus 1.
LinuxBIOS, however, does, and the 1022:746b device shows up on bus 1 in
linux
We're seeing an interesting problem here. 2.4.22 appears to want to rely
on ACPI tables for information on hyperthreading. Diffs seem to show that
the linux code that works directly with the hardware to work out
hyperthreading is gone.
What's happened now is that a dell box, without acpi bios
On Tue, 9 Sep 2003, Adam Agnew wrote:
>
> Funny you should ask. I was just preparing 2.4.22 again. It does detect 4
> processors, though it gives them rather strange numbers. This might be
> normal?
the numbers look ok.
Now I'm more confused than ever. Why would linuxbios work, and the Dell
w
On Tue, 9 Sep 2003, Adam Agnew wrote:
> Are there currently any elf loaders that boot under linuxbios which will
> let you change the default command line in kernel's made with mkelfImage
> from the serial console?
no, but I can try to find my hack which lets you change it interactively
with the
On 9 Sep 2003, Eric W. Biederman wrote:
> For that I cannot think of a reasonable explanation. I will have to look
> and verify this. I am pretty certain I booted a kernel after I made those
> changes..
are you on 2.4.21? I'll get the serial output (node is not on ethernet
yet)
thanks
ron
On Wed, 10 Sep 2003, Stefan Reinauer wrote:
> Is there any solution except stripping down?
we need a way to set it up so the linuxbios compressed payload is BELOW
linuxbios in memory.
That would buy a lot of room. I have not looked at this yet.
ron
__
On 10 Sep 2003, Eric W. Biederman wrote:
> There are a lot of good reasons for keeping LinuxBIOS within 64K. The
> two top ones are to limit code bloat and because startup is very
> tricky if you don't fit into 64K.
true, but ... :-)
> One thing you can look at is to strip down the debugging me
On Wed, 10 Sep 2003, Stefan Reinauer wrote:
> I got it compiling now with a log level of 7, but unfortunately it
> doesnt produce much output with that:
> LinuxBIOS-1.1.4.0Fallback Mit Sep 10 15:13:38 CEST 2003 starting...
what are you trying to debug? What I've done is this:
set MAXIMUM_CONSOL
On Thu, 11 Sep 2003, Stefan Reinauer wrote:
> > Correct. It is a little better on the HDAMA. But currently there are
> > some options that don't seem to work properly when I move them in closer.
>
> The above was taken from the hdama CVS.
> So is there a difference for the build process whether
On Fri, 12 Sep 2003, Stefan Reinauer wrote:
> looking at the big picture again and again, I don't think that
> nesting hypertransport devices when doing the chain description is a
> very good idea as it gives us some limitations.
you mean nesting them in the config file? I agree. It is not a good
On Fri, 12 Sep 2003, Stefan Reinauer wrote:
> creating a linuxbios.rom file in the build target directory that
> consists of the 2 concatenated romimages "normal" and "fallback"
> This way it's now possible to build several roms with "buildrom"
> that take the specified "romimage"s that were built
you could just buy one of these boards direct from cwlinux.com, as they
come with linuxbios pre-loaded. Saved work.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Sat, 13 Sep 2003, Craig C. Forney wrote:
> It successfully made romcc, but when it tried to run it to make either
> the failover or normal rom, it gets the following error:
> reset_test.c:13,111: 0x1e43570 copy Internal compiler error: bad
> type passed to copy
romcc is sensitive to the
On Mon, 15 Sep 2003, Stefan Reinauer wrote:
> buildrom
> size ROM_SIZE
> data ./lsiscsifw 65536
? What is that data thing?
ron
> image normal NORMAL_SIZE
no, you need this info when you build the board, it can't move here.
> Or maybe it makes sense to move the payloads into
On 15 Sep 2003, Eric W. Biederman wrote:
> > romcc is sensitive to the version of linux you are running at present.
>
> Ron how so? If romcc compiles it should work. I don't have any
> excuse for romcc to behave different depending on what compiler
> compiles it.
it makes no sense to me eithe
On 15 Sep 2003, Eric W. Biederman wrote:
> Either I am not executing this, in my configuration file. Or
> it works fine for me with python2.1 python2.2 and python2.3
I'll look at version, I just hit this and then had to go to work.
ron
___
Linuxbios
I think the USB stuff is of interest. I'm clueless how to write the
support for USB however, but I think it's worth somebody looking at it.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 16 Sep 2003, Niki Waibel wrote:
> i am currently playing with this. my epia-m has no DIP32 socket. i
> decided to use a DIP2PLCC adapter to use the MD2802-D08. so i can plug
> it directly into the bios socket.
please remember, getting to work in the socket is the easy part. Getting
epia
On Tue, 16 Sep 2003, Gregg C Levine wrote:
> Actually gentlemen, and ladies, no it is not. I have available for
> this system a USB Key Drive, from Memorex, and a CF reader, also from
> them. To use them under Linux, I need to turn on SCSI, and USB-Mass
> drive support. Also, the mass drive functi
On Tue, 16 Sep 2003, Stefan Reinauer wrote:
> Is there any need in going 64bit for the LinuxBIOS C payload on Opteron?
> Since the kernel does long mode switching itself this should not be the
> case, but maybe there are different opinions.
I think maybe when we start putting > 4 GB memory on the
On Tue, 16 Sep 2003, Stefan Reinauer wrote:
> * ron minnich <[EMAIL PROTECTED]> [030915 16:51]:
> > On Mon, 15 Sep 2003, Stefan Reinauer wrote:
> >
> > > buildrom
> > > size ROM_SIZE
> > > data ./lsiscsifw 65536
> >
> > ?
On Tue, 16 Sep 2003, ron minnich wrote:
> On Tue, 16 Sep 2003, Stefan Reinauer wrote:
>
> > * ron minnich <[EMAIL PROTECTED]> [030915 16:51]:
> > > On Mon, 15 Sep 2003, Stefan Reinauer wrote:
> > >
> > > > buildrom
> > > > size R
On Tue, 16 Sep 2003, Niki Waibel wrote:
> where can i get more info in how to init the mem on a
> epia-m? do i have to rev eng the bios?
>
read the linuxbios source, of course!
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.
On Tue, 16 Sep 2003, Niki Waibel wrote:
> where can i get more info in how to init the mem on a
> epia-m? do i have to rev eng the bios?
src/northbridge/via/vt8601/ipl.S is code that worked for the vt8601 2
years ago for DoC uses.
Not guaranteed to work with all DRAM. The 8601 is very tricky.
On Tue, 16 Sep 2003, Niki Waibel wrote:
> i think that the CLE266 (epia-m) is quite different then the vt8601.
> right now i've no idea about northbringes, but i hope that will change soon :)
doubtful, I have found lots of reuse of cores in these norhtbridges. But
I'm willing to be convinced :-)
On Tue, 16 Sep 2003, Stefan Reinauer wrote:
> This could be done using the Opterons PAE feature. Currently I see a
> tradeoff between LinuxBIOS image size and the design conflict when going
> away from 16bit firmware on 32bit systems while staying with 32bit on
> a 64bit platform.
this won't last
We've had no real luck building etherboot here lately. I'm not sure what's
wrong, but we get the same problems you do.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Wed, 17 Sep 2003, Andrew Ip wrote:
> More steps are required to init DDR. It might not fit
> in 512 bytes.
oops, I forgot the DDR nightmare. I think DoC is out for EPIA-M.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.or
Wow, I keep thinking sourceforge is fixed, and it keeps not being fixed.
OK, I'll try to do something about this (again)
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Wed, 17 Sep 2003, Niki Waibel wrote:
> what about haveing bios savior + DoC in a mb _and_
> connecting the bios savior switch to an address pin...
which address pin? where are you going to find it? I've not had good luck
with adding wires to these boards -- we've done it (see the web page) bu
On Wed, 17 Sep 2003, Niki Waibel wrote:
> could you send me / point me to some more info about init a ddr?
look at the linuxbios ddr code ;-)
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Wed, 17 Sep 2003, Niki Waibel wrote:
> yes. i got the point. but to be sure we need to know _how_ a ddr
> is initialized. so the question is -- who knows how to init a ddr?
we do. It's all over the newer mobos.
ron
___
Linuxbios mailing list
[EMAIL
On Wed, 17 Sep 2003, Jeffrey Knight wrote:
> I noticed on the linuxbios site that there was some suceess with
> linuxBIOS on an IBM T22 thinkpad. Nice!
no, sorry, there was only failure. IBM (Thinkpad division) has no interest
in linuxbios.
> If the installation was pretty smooth, I was think
On Fri, 19 Sep 2003 [EMAIL PROTECTED] wrote:
> Is it possible to extract the VideoBIOS from the XpressROM and use it
> somehow like in the EPIA ?? If yes has anyone done it?
It ought to work but I don't know if anyone has done it.
ron
___
Linuxbios mai
On Sat, 20 Sep 2003, rimy2000 wrote:
> Has the util/vgabios bug fixed?
which one?
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
we're working the lp0 issue.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
And HOWTO on these last steps, with sample kernel .config, is most
welcome.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Mon, 22 Sep 2003, bendany wrote:
> biosint: ip 0x3 cs 0x0 flags 0x46
> biosint: Unsupport int #0x6
> biosint: # 0x6, eax 0x0 ebx 0x10 ecx 0x20 edx 0x9d2e
> biosint: ebp 0x12060 esp 0xff6 edi 0xe0ac esi 0x846a2
> biosint: ip 0x3 cs 0x0 flags 0x46
> biosint: Unsupport int #0x6
> biosint: # 0x6, e
I think you should get memtest86, set it up to run on serial console, and
see if it works or not.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Mon, 22 Sep 2003, Bernd Modeker wrote:
> Is there anyone who solved this problem for SC1200?
not yet. If you have a copy of the vgabios binary for that hardware you
could try seeing if it would work.
The vga register problem is a mess, as the vendors rarely want to help.
ron
_
this these.
ron
/*
* $Id: rdcmos.c,v 1.1 1998/09/24 21:08:20 hendriks Exp $
*/
#include
#include
#include
#include
static inline
unsigned char readreg(int regno) {
outb(regno, 0x70);
return inb(0x71);
}
static inline
void writereg(int regno, unsigned char val) {
outb(regno, 0x70);
On Mon, 22 Sep 2003, Niki Waibel wrote:
> i've never used memtest86.
make memtest86 the payload. be sure to build with serial console only.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
I just committed various patches that have allowed us here to use VGA on
the M800
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
need more info.
What is the chip that is in the socket already? Are you trying to burn a
49F in a slot that won't support it?
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Mon, 22 Sep 2003, Damien Charlet wrote:
> My original BIOS is a 39SF020 A.
>
> According to http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionSheet.html I
> got the good savior for epia (better double check !).
> You don't think so ?
I don't think that 39F and 49F are compatible.
r
david hendriks has now built linuxbios from scratch, from the cvs tree,
and it all works with graphics etc.
ide is still not working well.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
fixes welcome. This is CF that is failing. Actually it reads the data and
the data is fine, but when it jumps to the payload nothing happens.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 23 Sep 2003, Andrew Ip wrote:
>
> > fixes welcome. This is CF that is failing. Actually it reads the data and
> > the data is fine, but when it jumps to the payload nothing happens.
> Have you tried different CF? Different CF behave differently. Some CF
actually, as near as we could
On Tue, 23 Sep 2003, Andrew Ip wrote:
> > actually, as near as we could tell the data was getting in to memory. But
> > once it jumped to the payload it never came back.
> Interesting. What payload are u using? I have been using etherboot which
> is pretty stable. However, Filo will be my next
I think you have found a bug, but we need to let andrew ip take a close
look. I would say your patch is correct as well.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
I find myself getting confused about all the EPIA boards and their
configurations.
Can someone help fill this in?
nameCPU Extension Speed RAM
EPIA-M C3 3DNOW 800 Mhz SDRAM
That's all I know :-)
ron
_
On Tue, 23 Sep 2003, Niki Waibel wrote:
name CPU Extension Speed RAM remarks
EPIA-M C3 3DNOW 800 Mhz SDRAM
EPIA-M C3 3DNOW 600 MHz SDRAM fanless
> # cat /proc/cpuinfo
> processor : 0
> vendor
On Tue, 23 Sep 2003, jay wrote:
> Is the list of motherboards on the linuxbios status page up to date? I
> am just curious, since it seems like a lot of mainstream boards (asus,
> abit, etc) are not listed there, but I would expect them to be. Also,
> with the K8 support, what motherboard is tha
On Tue, 23 Sep 2003, Bernd Modeker wrote:
> I tried the following bios which I extracted from insyde bios:
>
> sh-2.05b# ./testbios elpin.vga -d 94
> running file elpin.vga
> No size specified. defaulting to 32k
> No base specified. defaulting to 0xc
> No initial
On Tue, 23 Sep 2003, Niki Waibel wrote:
> any idea why linuxbios is not starting on the epia-m 600?
> i run memtest86 -- all tests (took about 24hours ;-) -> everyting ok.
> (run memtest86 from lilo).
> i also tried the patch of Ian Smith <[EMAIL PROTECTED]>.
ok, so you did memtest86 as a payload
name CPU Extension Speed RAM remarks
EPIA C3 3DNOW 800 Mhz SDRAM
EPIA C3 3DNOW 600 MHz SDRAMfanless
EPIA-MC3 3DNOW 933 MHz DDR-SDRAM
Is this more accurate now?
what is
On 23 Sep 2003, Justin Cormack wrote:
> Thats really great. Though I am *still* waiting for my Tyan boards to
> actually arrive. Maybe I will cancel my order and reorder with
> linuxbios. Is there a different part number, or how does one specify?
supported on the S2880 and S2885
ron
___
On Tue, 23 Sep 2003, Bernd Mödeker wrote:
> the internal vga pci device at 0:12.4 should be found when you write
> 0x80009400 to pci index reg
> 0xcf8. After that the value 0x0504100b should be returned at 0xcfc as vendor
> id (0x100b) and device id (0x0504).
> After single stepping this return va
On Tue, 23 Sep 2003, ron minnich wrote:
> > c000:0124 ed INEAX,DX
no 66 prefix means it really is 16 bits, btw.
Anyway, can you check and see if there is a vga enable? there almost
always is in these chipsets
On Tue, 23 Sep 2003, Bernd Mödeker wrote:
> I could'nt follow. What do you mean?
frequently, in the north bridge, there is a magic bit in some
register in device 0:0.0 that enables the VGA hardware. If you don't set
it, the VGA hardware will act like it is not there when you probe it.
ron
___
On Wed, 24 Sep 2003, SONE Takeshi wrote:
> I saw an old version of my fixes to idt.c and vgabios.c is commited.
> This version does not pass dev/busfn to the VGABIOS correctly.
send me the fix. I thought this was the right one. Sorry.
ron
___
Linuxbio
On Wed, 24 Sep 2003, Peter Stuge wrote:
> On Tue, Sep 23, 2003 at 10:19:56PM +0200, Bernd Mödeker wrote:
> > > Anyway, can you check and see if there is a vga enable? there almost
> > > always is in these chipsets.
> > The vga device is enabled. If I use devmem I can read the vendor and device
> >
On Wed, 24 Sep 2003, Niki Waibel wrote:
> instead of copying to ram, execute the code directly from the rom?
yes indeed, the original way we used to run linuxbios.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/l
On Wed, 24 Sep 2003, Niki Waibel wrote:
> no. executed memtest86 from lilo -- not as payload.
ah, so we really don't know anything from that test. OK.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxb
we need to really fix this epia platform. This juggling of constants is
the wrong thing to do. If somebody has the time they need to go in and get
rid of the magic numbers use the SPD properly.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://w
what machine are you on, what install of what os?
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
David Hendriks has tested and I have committed these new idt.c and
vgabios.c
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
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
On Thu, 25 Sep 2003, Stefan Reinauer wrote:
> * 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.
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
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.
Recall that we no longer allow multiple settings of o
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
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
these
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 mai
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,
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 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 bot
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.
thank
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 too
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 shoul
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 >
I knew this would be a bit of work, but it is worth it as it is flushing
out "K8 and SMP" assumptions in the tree.
I really would appreciate it if somebody could look at the early smbus
code.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://
OK, where we are is this: there is a freebios2 version for the via/epia.
It builds. I have set it up so memory config *should* *be* what we have
now, i.e. static. But this will get us to status quo, and then we can look
at SPD etc.
ron
___
Linuxbios
I could use a fragment of code that makes the uart sane.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On Fri, 26 Sep 2003, ron minnich wrote:
> I could use a fragment of code that makes the uart sane.
never mind, done.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
comes up with POST 10. That's it.
But hey, I didn't expect more yet ... this is a start :-)
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
up to postcode 12
rno
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
getting serial output.
Dies after copy to ram. Gee, what a shock :-)
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
here is what I get:
0
LinuxBIOS-1.1.4.0Fallback Fri Sep 26 16:04:07 MDT 2003 starting...
SMBus controller enabled
vt8601 init starting
0800 is the north
vt8601 done
LinuxBIOS-1.1.4.0Fallback Fri Sep 26 16:04:07 MDT 2003 starting
On Sat, 27 Sep 2003, Stefan Reinauer wrote:
> This did help indeed. Is there any good reason not to reverse the
> probing per default? Ron, Eric?
I'm going to defer to Eric on this, as I am not sure.
ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
ht
OK, here is where I am.
Here is the start of the key function
in src/northbridge/via/vt8601/raminit.c
static void sdram_set_registers(const struct mem_controller *ctrl) {
static const uint16_t raminit_ma_reg_table[] = {
/* Values for MA type register to try */
0x, 0x8088, 0xe0ee,
401 - 500 of 1001 matches
Mail list logo
