[LinuxBIOS] buildrom tyan s2891 and LAB

[ron minnich]

I did a config for the 2891 with LAB, but all I see in deploy is this:
ls -l deploy/
total 7280
-rw-r--r-- 1 rminnich rminnich  905680 2007-11-06 19:36 bzImage
-rw-rw-r-- 1 rminnich rminnich  272384 2007-11-06 19:38 initrd.uncompressed
-rw-rw-r-- 1 rminnich rminnich  879963 2007-11-06 19:38 lab-payload.elf.lzma
-rw-r--r-- 1 rminnich rminnich 2108666 2007-11-06 19:38
lab-payload-uncompressed.elf
-rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38 tyan-s2891.rom
-rw-r--r-- 1 rminnich rminnich 2242990 2007-11-06 19:36 vmlinux

And the  only linuxbios.rom I see is this:
ls -l ./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom
-rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38
./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom

So where is the romimage? What am I missing?

ron

[Myles Watson]

> I did a config for the 2891 with LAB, but all I see in deploy is this:
> ls -l deploy/
> total 7280
> -rw-r--r-- 1 rminnich rminnich  905680 2007-11-06 19:36 bzImage
> -rw-rw-r-- 1 rminnich rminnich  272384 2007-11-06 19:38
> initrd.uncompressed
> -rw-rw-r-- 1 rminnich rminnich  879963 2007-11-06 19:38 lab-
> payload.elf.lzma
> -rw-r--r-- 1 rminnich rminnich 2108666 2007-11-06 19:38
> lab-payload-uncompressed.elf
> -rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38 tyan-s2891.rom
> -rw-r--r-- 1 rminnich rminnich 2242990 2007-11-06 19:36 vmlinux
>
> And the  only linuxbios.rom I see is this:
> ls -l ./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom
> -rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38
> ./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom
>
> So where is the romimage? What am I missing?
> ron

Check s2891deploy/

I think the s2891 config makes its own directory.

Myles>

[Ward Vandewege]

On Wed, Nov 07, 2007 at 07:21:33AM -0700, Myles Watson wrote:
> > I did a config for the 2891 with LAB, but all I see in deploy is this:
> > ls -l deploy/
> > total 7280
> > -rw-r--r-- 1 rminnich rminnich  905680 2007-11-06 19:36 bzImage
> > -rw-rw-r-- 1 rminnich rminnich  272384 2007-11-06 19:38
> > initrd.uncompressed
> > -rw-rw-r-- 1 rminnich rminnich  879963 2007-11-06 19:38 lab-
> > payload.elf.lzma
> > -rw-r--r-- 1 rminnich rminnich 2108666 2007-11-06 19:38
> > lab-payload-uncompressed.elf
> > -rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38 tyan-s2891.rom
> > -rw-r--r-- 1 rminnich rminnich 2242990 2007-11-06 19:36 vmlinux
> >
> > And the  only linuxbios.rom I see is this:
> > ls -l ./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom
> > -rw-rw-r-- 1 rminnich rminnich 1011712 2007-11-06 19:38
> > ./work/linuxbios/svn/targets/tyan/s2891/s2891/linuxbios.rom
> >
> > So where is the romimage? What am I missing?

The tyan-s2891.rom file in deploy/ is the image; it expects you to prepend
the 36K vga rom to make it a full megabyte. The 36K vga rom is identical
across S2881, S2882 and S2891 (and possibly other Tyan servers; those are the
three models I have access to).

I really need to make work of that kconfig option for 'add vga bios after
compile'.
> Check s2891deploy/
>
> I think the s2891 config makes its own directory.

Uhm, no :)

Thanks,
Ward.

[Jordan Crouse]

On 07/11/07 09:31 -0500, Ward Vandewege wrote:
> I really need to make work of that kconfig option for 'add vga bios after
> compile'.

I'm assuming its not freely distributable?  If it is, then we can wget
it and prepend it automagically.  If its not, then we have two courses
of action:

1) user manually copies a file into deploy, calling it vga.bin.  buildrom
automatically prepends any file called vga.bin to the ROM (to further make
it configurable, each platform could specify the filename to prepend).

2) User specifies the location of the file with a config option, buildrom
grabs the file from there and prepends it (like we do with the "custom
payload" right now).

Thoughts?

Jordan

[Corey Osgood]

Jordan Crouse wrote:
> On 07/11/07 09:31 -0500, Ward Vandewege wrote:
> > I really need to make work of that kconfig option for 'add vga bios after
> > compile'.
>
> I'm assuming its not freely distributable?  If it is, then we can wget
> it and prepend it automagically.  If its not, then we have two courses
> of action:
> user manually copies a file into deploy, calling it vga.bin.  buildrom
>
> automatically prepends any file called vga.bin to the ROM (to further make
> it configurable, each platform could specify the filename to prepend).
> User specifies the location of the file with a config option, buildrom
>
> grabs the file from there and prepends it (like we do with the "custom
> payload" right now).
>
> Thoughts?
>
> Jordan

3) wget the stock bios and amideco/awardeco, and extract/prepend the vga
bios automatically

-Corey

[Jordan Crouse]

On 07/11/07 11:27 -0500, Corey Osgood wrote:
> Jordan Crouse wrote:
> > On 07/11/07 09:31 -0500, Ward Vandewege wrote:
> > > I really need to make work of that kconfig option for 'add vga bios after
> > > compile'.
> >
> > I'm assuming its not freely distributable?  If it is, then we can wget
> > it and prepend it automagically.  If its not, then we have two courses
> > of action:
> > user manually copies a file into deploy, calling it vga.bin.  buildrom
> >
> > automatically prepends any file called vga.bin to the ROM (to further make
> > it configurable, each platform could specify the filename to prepend).
> > User specifies the location of the file with a config option, buildrom
> >
> > grabs the file from there and prepends it (like we do with the "custom
> > payload" right now).
> >
> > Thoughts?
> >
> > Jordan
> wget the stock bios and amideco/awardeco, and extract/prepend the vga
>
> bios automatically

That scares me a little.  Obviously, using the VGA BIOS from the stock
BIOS is fair use, but to me, exercising fair use dictates that the user
know and chose to excercise their rights.  Automating the process seems
a little dodgy to me - the user will end up with a VGA BIOS by methods
uknown.  Its a gray area, but I think we don't really want to be in this
business.  With the lack of a clear distribution policy (and this is where
we should all thank SiS again for getting the ball rolling and providing
a good example), then I think its not to much to ask the user to explicity
chose to excercise their rights to fair use.

Jordan