Re: CONFIG_LB_MEM_TOPK

Svn diff to current tree.

Please check it. I will commit it some time next week.

Guys have problem with s2891, s2881, s2892, please try it by 

patch -p0 to the latest tree.

Changes
1. new CAR with copy data from cache to ram
2. new coherent_ht_car.c
3. new reset code for amd8111
4. new amd8111_early_ctrl without sysinfo...

Thanks

Yinghai Lu

--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios

Advantech SOM GX5333 commited

I just committed the support for the the SOM-2354 CPU board running on
a SOM-DB2301 base board.

MSR 20000018 was from the rumba setup which didn't work on this board.
 Current value was ripped from how XpressROM set it.  Other than that
all I had to change was the superIO.

The unit boots jumps to linubios and looks for the vsabin which it
can't find since its not there.

What's next?

I have also made a little bit of progress on compiling the VSA. 
OpenWatcom has a 16-bit compiler and I've been hacking the makefile(s)
to get it to work.  OWC has a cl compability mode but IFAICT its 32bit
only.  I've attemped to translate the switches.

I'm currently at the point of trying to figure out how to feed the OWC
linker all the object files.

--
Richard A. Smith
--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios

Re: Geode SC22000

* Per Hallsmark <perh <at> t2data.se> [060331 14:16]:
> The LB base is svn ver 2171, I've got a 71K big patch for it.
> How do I contribute it to LB tree?

Just send an "svn diff" as an attachment to this list.

> Q1: The source code files often include source files again instead
> of like building object modules that are later linked together.
> Why something like this? It seems odd to me as an perhaps oldschool
> C programmer.

That's done in the romcc compiled code. The reason is that you can only
know how the code looks like as a whole, the single parts look pretty
different depending on the register pressure. Remember: This code is
compiled to assembler code that does not use _any_ memory but runs in
registers only.

> Q2: Why does the LB project need a special compiler?
> I've done numberous of firmware stuff and ordinary gnu tools have a
> good job so far.
> Must admit though that these hasn't been x86 which of course has it
> special boot mode, but there exist "standard" tools for that as well.
> (RPM package dev86 for example)

It does not _need_ one. The thing is, we don't want to write ram
initialization code for complex systems (such as the amd64) in assembler
but instead in more readable and understandable C code.
Since, consequentially, there is no RAM during RAM initialization, you
need to make sure the code fits into registers only.

Re: Advantech SOM GX5333 commited

> I just committed the support for the the SOM-2354 CPU board running on
> a SOM-DB2301 base board.
>
> MSR 20000018 was from the rumba setup which didn't work on this board.
>  Current value was ripped from how XpressROM set it.  Other than that
> all I had to change was the superIO.
>

I have better version of programming MSR 20000018 around. I will try
to commit it next week. Does your board have SPD?

> The unit boots jumps to linubios and looks for the vsabin which it
> can't find since its not there.
>
> What's next?
>

Put your VSAINIT.BIN+SYSMGR.BIN at the bottom of your flash (like what
we did with VGA BIOS). Point the address where vsmsetup want to look
for VSM to the bottom of your flash. It sould be able to find the
vsa. BTW, the code on the current SVN has some serious bug (forget to
call setup_realmode_idt() before vsmsetup()) so it will crash soon
after jump into VSA. I will commit it fix next week.

I think there are still one or two MSR we have to program and probably
we need big real mode instead of the real mode for VSA to work. I will
dig into it more with the JTAG debugger later.

> I have also made a little bit of progress on compiling the VSA.
> OpenWatcom has a 16-bit compiler and I've been hacking the makefile(s)

Re: Geode SC22000

> Hello LB people,
>
> First, a great thank for the quick boost I had from your project
> in creating a special firmware for our project.
>
> I've ported LB to a SC2200 based platform, NCG266 (you can see some
> old photos at www.nano-system.com) The jump to the load just takes
> a couple of secs instead of like a minute with the Insyde BIOS...
>

Is there any reason you are working on an EOL product?

Ollie

--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios

Re: Advantech SOM GX5333 commited

Dear,

What about vsa legal questions ?
Are you using the source code available from insyde site ?
Has amd licensed VSA under GPL ?

Thanks.

Jardel.

>> I just committed the support for the the SOM-2354 CPU board running on
>> a SOM-DB2301 base board.
>>
>> MSR 20000018 was from the rumba setup which didn't work on this board.
>>  Current value was ripped from how XpressROM set it.  Other than that
>> all I had to change was the superIO.
>>
>
> I have better version of programming MSR 20000018 around. I will try
> to commit it next week. Does your board have SPD?
>
>> The unit boots jumps to linubios and looks for the vsabin which it
>> can't find since its not there.
>>
>> What's next?
>>
>
> Put your VSAINIT.BIN+SYSMGR.BIN at the bottom of your flash (like what
> we did with VGA BIOS). Point the address where vsmsetup want to look
> for VSM to the bottom of your flash. It sould be able to find the

Re: Advantech SOM GX5333 commited

> Dear,
>
>
> What about vsa legal questions ?
> Are you using the source code available from insyde site ?
> Has amd licensed VSA under GPL ?
>

We got source code from AMD. It is not GPL but more like MIT/X.
I think we should be able to redistribute the source code but
I have to make sure again.

Ollie

--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios

Re: Geode SC22000

Hi again,

Ok, here comes the svn diff (towards 2171) attached.
It's quite big, had to add superio and southbridge setups
(along with it's attached devices) which is embedded in
the SC2200. It was unfortunally not just a small port of
the current GX1...
There is some extra POST codes inserted to follow code flow,
perhaps this should be removed before adding patch into live tree.

I've also started a (yet another) porting guide, intent
is to make it more detailed and also describe "obvious"
steps that perhaps is not so obvious for a linuxbios beginner.
(at least it wasn't for me  )

Have a GX3 eval board (ITX form) somewhere on my desk, will
be a good testdrive porting according to document.

I've seen some logs here on mailing list that have nice
timestamps in first column. Is there some standard support
for this in LinuxBIOS? (have searched around in code but
couldn't find it)

Stefan, thanks for you answers. I'm still a bit puzzled though
why PPC, ARM, XScale, MIPS manages same thing without romcc or similar.
Is memory setup done so very much different and is so much more
complex in x86? For my port, SC2200, it looks about same to me.
(could be because of my embedded background, most targets have
 had defined memory size so mem sizing isn't a problem...)

Re: help

* Neil <myneil <at> gmail.com> [060403 13:27]:
> Hi,
> I am a freshman to linuxbios. And I am preparing porting linuxbios on my
> motherboard .
> My northbridge is Server works (SWC HT2000),and southbridge is Serverworks
> HT-1000, I don't know if it supports the chipset? could you please tell me ?
> and I cannot find relate source code in the source tree , should I create it
> myself ?

I think its the same as the Broadcom BCM5780/85. Yinghai Lu did the port
iirc.

Stefan

-- 
coresystems GmbH · Brahmsstr. 16 · D-79104 Freiburg i. Br.
      Tel.: +49 761 7668825 · Fax: +49 761 7664613
Email: info <at> coresystems.de  · http://www.coresystems.de/

--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios

linuxbios on nodes?

Hi everyone,

regarding linuxbios:
Do I have to load linuxbios on both "server PC" and nodes,
or can I get away with loading it on the nodes only?

ps. if this is any help, I am planning on using Clustermatic ..

--

-- 
linuxbios mailing list
linuxbios <at> linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios