Here is the patch file that should create a Makefile.distro in the
target directory and then include this file as part of the make
process. It checks for the buildid option for ld using awk in
buildtarget script. Then sets the appropriate flag in the file.
I do not check to see if the Makefile.distro is "current". It just
checks to see if one is present or not.
--
/*********************
Marc Karasek
MTS
Sun Microsystems
mailto:marc.karasek@sun.com
ph:770.360.6415
*********************/
On 02/01/08 09:32 -0200, Omar Esteves Duarte Filho wrote:
> Thank you for the support and sorry for the inconvenience, Jordan. You are
> right: this is off-topic.
First - please - stop using the term 'VGA'. VGA is a very specific
standard for video display (http://en.wikipedia.org/wiki/VGA). There is no
VGA here. By using the term, you muddle the discussion.
> After some investigation here, i've finally got VGA output (both text
> console and X)! In the end, it seems that there is some problem with the
> lxfb driver. I was trying to set up the VGA with the video boot parameter in
> the kernel command line ("lxfb.mode_option=..."). But, it did not work.
> However, the video output works if "fbset 640x480-60", for instance, was
> previously typed. The fbset tool initializes the VGA with different timing
> parameters. Below is the VGA timing parameters right after the boot process
> is complete and there's still no VGA output:
mode_option is only valid when you load the driver as a module. When running
with the driver built in, then you specify the mode on the command line,
as detailed in Documentation/fb/modedb.txt. The correct way to specify the
mode on the command line is as follows:
video=lxfb:<xres>-<yres>-<bpp>@<refresh>
I also noted that you were specifying vga=<number> on your command line - if
the vesa framebuffer is also installed in your kernel (as it would be with
a normal Ubuntu kernel), then that will cause the VESA framebuffer to be
loaded first (which would of course, fail). The lxfb would be loaded as
well, but registered as the second framebuffer (if you have your kernel
output from dmesg, you should be able to see this happen).
The fbset you did below would kick the second driver and have it take over
the console from the failed primary driver.
> root@ubuntu-LX800:~# fbset -i
>
> mode "640x480-60"
> # D: 25.175 MHz, H: 31.469 kHz, V: 59.940 Hz
> geometry 640 480 640 480 16
> timings 39682 48 8 25 2 88 2
> rgba 5/11,6/5,5/0,0/0
> endmode
This is the mode specified in lxfb_core.c - this is the correct timings for
the Geode for the VESA mode 640x480@60.
> Then, fbset is used to adjust the video mode:
>
> root@ubuntu-LX800:~# fbset 640x480-60
> root@ubuntu-LX800:~#
>
>
> After that, VGA output works and timing parameters are checked again:
>
> root@ubuntu-LX800:~# fbset -i
>
> mode "640x480-60"
> # D: 25.175 MHz, H: 31.469 kHz, V: 59.940 Hz
> geometry 640 480 640 480 16
> timings 39722 48 16 33 10 96 2
> rgba 5/11,6/5,5/0,0/0
> endmode
This is the mode that is listed in the file /etc/fb.modes - which is a
set of generic timings provided by Ubuntu. Both timings are actually
correct - if you were to run fbset and set the previous timings, they would
work. What you are seeing is a side effect of a poorly configured
kernel.
Jordan
Phani Babu Giddi wrote:
> Hi Corey,
>
> Thanks for your reply but I am not clear. Let me list the steps, may
> be that will explain the problem I see.
>
> 1. I have a host target environment
> 2. I build Linux Kernel image with initrd on the host
> 3. I also build the root file system on the host
> 4. Now I build Linux BIOS and specify the Linux Kernel as payload.
> 5. So at this point I have the .bin/.rom for Linux BIOS and an image
> file for the root file system.
> 6. So my question was how do I get this on the flash device. Do I have
> to use an external programmer for this ? Because there is nothing on
> the target for me to run flashrom.
Yep, you can use an external programmer, or you can use some other board
that's compatible with flashrom and your flash chip, by hot swapping the
flash chips.
-Corey
On 26/12/07 10:50 -0200, Omar Esteves Duarte Filho wrote:
> Jordan,
>
> Thank you again!
>
> I removed splash and quiet form the menu.lst and added "console=tty0
> console=ttyS0,115200", as you can see below:
>
> title Ubuntu 7.10, kernel 2.6.23.9-geodelx-fb
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.23.9-geodelx-fb
> root=UUID=a4e4ac87-c677-45e1-a
> a21-1e4654feac95 ro vga=771 console=tty0 console=ttyS0,115200
> initrd /boot/initrd.img-2.6.23.9-geodelx-fb
>
> I got some success here: startx works, but there's still no vga console
> before X starts. I think there is some problem with the lxfb driver because,
> if i switch the line " Device "AMD" " by "Device "Generic Video Card"" in
> the xorg.conf file, I get no result. lxfb and fbcon are built into the
> kernel.
This is starting to get off topic for the linuxbios list, but I'll answer
it here since others might have the same problem.
X and the kernel have nothing to do with one-another - they are completely
seperate entities. If you do not see the text console (and the penguin)
once the kernel has started, then something has gone wrong. Please send
the dmesg output from your kernel, and your kernel config.
Jordan
Dear All,
I'm terribly sorry that I just found I've mistakenly configured the dram MA
Map Type, and now memtest
showed no errors. But I still have to reduce the mem size when reporting to
system through ram_resource
or filo couldn't be started. I have disabled the integrated graphics card
and the agp, so I don't think the top
memory should be reserved for frame buffer.
---------- Forwarded message ----------
From: Phani Babu Giddi <phanig(a)gmail.com>
Date: Jan 1, 2008 8:29 AM
Subject: Re: [LinuxBIOS] flashrom on the host or target ?
To: Corey Osgood <corey.osgood(a)gmail.com>
Hi Corey,
Thanks for your reply but I am not clear. Let me list the steps, may be that
will explain the problem I see.
1. I have a host target environment
2. I build Linux Kernel image with initrd on the host
3. I also build the root file system on the host
4. Now I build Linux BIOS and specify the Linux Kernel as payload.
5. So at this point I have the .bin/.rom for Linux BIOS and an image file
for the root file system.
6. So my question was how do I get this on the flash device. Do I have to
use an external programmer for this ? Because there is nothing on the target
for me to run flashrom.
Regards,
Phani
On Dec 31, 2007 11:07 PM, Corey Osgood <corey.osgood(a)gmail.com> wrote:
> Phani Babu Giddi wrote:
> > Hello All,
> >
> > I am trying to understand how to access the flash chip on
> > the mainboard for the very first time. Most of the documentation on
> > Linux BIOS talks about using "flashrom" but I am confused, are we
> > suppose to use this on the target ( mainboard) or host. If its host
> > are is there a way one can access the flash disk from the host, I have
> > looked into the Hardware Tools that have been suggested for Linux BIOS
> > but I could not find anything related to this. If flashrom utility is
> > supposed to be used on the target, then how is that possible because
> > there is no image on the flash device.
> >
> > BIOS Saviour and other tools come into picuture if there is some thing
> > already on the flash chip.
> >
> > So am I suppose to select the payload as etherboot and then try
> > flashing the device for the first time. Or else I am suppose to use an
> > external programmer for this.
> >
> > If we succeed in getting the BIOS with the payload into the flash
> > device what about the root file system and partitions and any other
> > info. The question might sound elementary to most of you but I would
> > appreciate your help.
> >
> > To summarize the question is about getting bare bones board up and
> > running for the very first time.
> >
> > Regards,
> > Phani
>
> It doesn't matter. As long as you have the chip that you intend to flash
> in the system you run flashrom on, and use compatible hardware (both
> with the chip and flashrom), then you can flash literally any image onto
> any flash chip. It doesn't matter if the system you use to flash has
> completely different hardware then the image's intended target.
>
> -Corey
>
> PS Happy new year, everyone!
>
Hello All,
I am trying to understand how to access the flash chip on the mainboard for
the very first time. Most of the documentation on Linux BIOS talks about
using "flashrom" but I am confused, are we suppose to use this on the target
( mainboard) or host. If its host are is there a way one can access the
flash disk from the host, I have looked into the Hardware Tools that have
been suggested for Linux BIOS but I could not find anything related to this.
If flashrom utility is supposed to be used on the target, then how is that
possible because there is no image on the flash device.
BIOS Saviour and other tools come into picuture if there is some thing
already on the flash chip.
So am I suppose to select the payload as etherboot and then try flashing the
device for the first time. Or else I am suppose to use an external
programmer for this.
If we succeed in getting the BIOS with the payload into the flash device
what about the root file system and partitions and any other info. The
question might sound elementary to most of you but I would appreciate your
help.
To summarize the question is about getting bare bones board up and running
for the very first time.
Regards,
Phani
