On Fri, 12 Sep 2008, Joseph Smith wrote:
On Fri, 12 Sep 2008 00:24:32 -0400, "Corey Osgood" <[EMAIL PROTECTED]>
wrote:
On Fri, Sep 12, 2008 at 12:19 AM, Joseph Smith <[EMAIL PROTECTED]>
wrote:
On Fri, 12 Sep 2008 00:13:18 -0400, "Corey Osgood"
<[EMAIL PROTECTED]>
wrote:
On Thu, Sep
On Fri, 12 Sep 2008 00:24:32 -0400, "Corey Osgood" <[EMAIL PROTECTED]>
wrote:
> On Fri, Sep 12, 2008 at 12:19 AM, Joseph Smith <[EMAIL PROTECTED]>
wrote:
>>
>>
>>
>> On Fri, 12 Sep 2008 00:13:18 -0400, "Corey Osgood"
> <[EMAIL PROTECTED]>
>> wrote:
>>> On Thu, Sep 11, 2008 at 10:31 PM, Peter Stu
On Fri, Sep 12, 2008 at 12:19 AM, Joseph Smith <[EMAIL PROTECTED]> wrote:
>
>
>
> On Fri, 12 Sep 2008 00:13:18 -0400, "Corey Osgood" <[EMAIL PROTECTED]>
> wrote:
>> On Thu, Sep 11, 2008 at 10:31 PM, Peter Stuge <[EMAIL PROTECTED]> wrote:
>>> Joseph Smith wrote:
So for Linux do you mean reading
On Fri, 12 Sep 2008 00:13:18 -0400, "Corey Osgood" <[EMAIL PROTECTED]>
wrote:
> On Thu, Sep 11, 2008 at 10:31 PM, Peter Stuge <[EMAIL PROTECTED]> wrote:
>> Joseph Smith wrote:
>>> So for Linux do you mean reading /etc/fstab to find the /boot label
>>> and going from there???
>>
>> No, that is a
On Thu, Sep 11, 2008 at 10:31 PM, Peter Stuge <[EMAIL PROTECTED]> wrote:
> Joseph Smith wrote:
>> So for Linux do you mean reading /etc/fstab to find the /boot label
>> and going from there???
>
> No, that is a much later problem.
>
> We are at the stage when all we know are physical hard drives, a
Jason Craven wrote:
> Wondering if coreboot support is available for my system,
Short answer: Not likely.
Send lspci output to possibly get a longer answer, but I think the
conclusion will be the same. (Not 100% sure though.)
//Peter
--
coreboot mailing list: coreboot@coreboot.org
http://www.c
Ok then it is settled. This is my direction on this. If anyone else has any
thooughts on this, please share.
--
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Joseph Smith wrote:
> Just wanted to add that this method would also cut us free from
> using any other kind of Boot Manger (GRUB).
FILO is already independent of GRUB.
> We wouldn't have to deal with any legacy "BIOS" stuff.
We already do not deal with any legacy BIOS stuff in FILO.
> I thin
Joseph Smith wrote:
> > Scanning for drives has been considered before but always dismissed
> > because it will potentially take a very long time for FILO to start
> > if it needs to wait for drives to start.
>
> Doesn't the drive have to start for FILO to invoke GRUB?
FILO never invokes GRUB. FI
On Fri, 12 Sep 2008 05:21:08 +0200, Peter Stuge <[EMAIL PROTECTED]> wrote:
> Joseph Smith wrote:
>> FILO searches for a filo.conf file on the first drive it finds
>
> Scanning for drives has been considered before but always dismissed
> because it will potentially take a very long time for FILO t
On Thu, 11 Sep 2008 23:07:32 -0400, Joseph Smith <[EMAIL PROTECTED]>
wrote:
>
> Starting a new thread on the FILO subject because it isn't really about
> "BIOS" stuff anymore. What about this theory. FILO searches for a
> filo.conf
> file on the first drive it finds in the first partition root
Joseph Smith wrote:
> FILO searches for a filo.conf file on the first drive it finds
Scanning for drives has been considered before but always dismissed
because it will potentially take a very long time for FILO to start
if it needs to wait for drives to start.
As an optional feature, everyone pr
Starting a new thread on the FILO subject because it isn't really about
"BIOS" stuff anymore. What about this theory. FILO searches for a filo.conf
file on the first drive it finds in the first partition root directory. If
it does not find filo.conf it prompts the user for a configuration. At the
Joseph Smith wrote:
> So for Linux do you mean reading /etc/fstab to find the /boot label
> and going from there???
No, that is a much later problem.
We are at the stage when all we know are physical hard drives, and we
want to look up where an operating system is, and how we start it.
The how m
On Thu, 11 Sep 2008 21:23:06 -0400, Joseph Smith <[EMAIL PROTECTED]>
wrote:
>
>
>
> On Fri, 12 Sep 2008 03:01:31 +0200, Peter Stuge <[EMAIL PROTECTED]> wrote:
>> Joseph Smith wrote:
>>> So, Peter do you have any ideas on how we could make this happen?
>>
>> Peter Stuge wrote:
>>> Do a compari
On Fri, 12 Sep 2008 03:01:31 +0200, Peter Stuge <[EMAIL PROTECTED]> wrote:
> Joseph Smith wrote:
>> So, Peter do you have any ideas on how we could make this happen?
>
> Peter Stuge wrote:
>> Do a comparison with all other disk labels that the composite of
>> Linux, BSD and Windows NT supports.
Joseph Smith wrote:
> So, Peter do you have any ideas on how we could make this happen?
Peter Stuge wrote:
> Do a comparison with all other disk labels that the composite of
> Linux, BSD and Windows NT supports.
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listi
>> I just want to make it boot like a bootloader should. A bootloader
>> should be able to boot a drive without specifing PATHS.
>
> Now this is an interesting discussion!
>
So, Peter do you have any ideas on how we could make this happen?
--
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.
Gregg Levine wrote:
> I've just been given an SIS based system. I'll know more about it
> when I get back from vacation, but is this older family supported
> on Coreboot? Or do I need to go back to either of the two original
> LinuxBIOS trees I've got someplace?
Please send lspci when you get back
Hello!
I've just been given an SIS based system. I'll know more about it when
I get back from vacation, but is this older family supported on
Coreboot? Or do I need to go back to either of the two original
LinuxBIOS trees I've got someplace?
Basically its the original family that I distinctly reme
Joseph Smith schrieb:
> are really opposed to. But, All the info to boot is laid out in the
> MBR/first sector of the Active Partition.
>
The first sector contains code. Code, that usually relies on BIOS
services to proceed (eg. to load its own config, to load the kernel, etc)
> 1. the MBR tells
>> mbrs/partition tables
>
> See how those two don't fit together?
>
Sorry bad terminoligy MBR/first sector of the Active Partition
>
>
>> I really think it is possible to take the data from the
>> mbr/partition table and manipulate it to our advantage, thus
>> bypassing ALL real mode interrup
Joseph Smith wrote:
> > state of the art
>
> mbrs/partition tables
See how those two don't fit together?
> I really think it is possible to take the data from the
> mbr/partition table and manipulate it to our advantage, thus
> bypassing ALL real mode interrupts. The problem would be if an OS
>
On 11/09/08 18:56 -0400, Joseph Smith wrote:
>
> OK Peter and Jordan...you have prevoked a challenge. Would eithor of you
> care to put a wager on the fact I bet I can get to the GRUB menu based on
> the MBR's data without using any kind of real mode interrupt handler with
> FILO???
Seeing as how
> As for a new standard I think we should start out by evaluating all
> current disklabel schemes to see what state of the art is, and how we
> can improve upon it.
>
Ahh, that is the whole point I'm trying to get accross. I have been
studying
mbrs/partition tables and how they work, and what dat
Joseph Smith wrote:
> Would eithor of you care to put a wager on the fact I bet I can get
> to the GRUB menu based on the MBR's data without using any kind of
> real mode interrupt handler with FILO???
I am not interested.
You will certainly not come anywhere near GRUB stage 1.5 without some
numb
Joseph Smith wrote:
> > If you want BIOS behavior, just use a BIOS.
>
> Dam it Peter, I don't want to make FILO into a "BIOS".
You want to make it act like one.
> I just want to make it boot like a bootloader should. A bootloader
> should be able to boot a drive without specifing PATHS.
Now th
OK Peter and Jordan...you have prevoked a challenge. Would eithor of you
care to put a wager on the fact I bet I can get to the GRUB menu based on
the MBR's data without using any kind of real mode interrupt handler with
FILO???
--
Thanks,
Joseph Smith
Set-Top-Linux
www.settoplinux.org
--
core
On Fri, 12 Sep 2008 00:19:11 +0200, Peter Stuge <[EMAIL PROTECTED]> wrote:
> Joseph Smith wrote:
>> > I think you should just use SeaBIOS.
>>
>> Nope. This will be a autoboot_mbr option of FILO. Here is how it
>> will work:
>
> So you're teaching FILO how to act like a BIOS.
>
> I will fight t
Previously when I was testing the jetway target, I found that the IDE
devices were always enabled, as the mainboard's Config.lb seems to
suggest would be the case.
Today, after running an 'svn up' and reverting the
src/southbridge/via/vt8237r to before the breakage in rev 3567, I found
that the ID
On 11/09/08 18:05 -0400, Joseph Smith wrote:
>
>
>
> On Thu, 11 Sep 2008 16:03:04 -0600, Jordan Crouse <[EMAIL PROTECTED]>
> wrote:
> > On 11/09/08 17:49 -0400, Joseph Smith wrote:
> >>
> >> OK,
> >> My JMP question is about copying a drives mbr to memory 0x7c00 and or
> >> 0x0600 at 512 byte
>
Joseph Smith wrote:
> > I think you should just use SeaBIOS.
>
> Nope. This will be a autoboot_mbr option of FILO. Here is how it
> will work:
So you're teaching FILO how to act like a BIOS.
I will fight that patch hard. I'm afraid I think this design is
completely misguided.
Joseph Smith wrot
On Thu, 11 Sep 2008 16:03:04 -0600, Jordan Crouse <[EMAIL PROTECTED]>
wrote:
> On 11/09/08 17:49 -0400, Joseph Smith wrote:
>>
>> OK,
>> My JMP question is about copying a drives mbr to memory 0x7c00 and or
>> 0x0600 at 512 byte
>> blocks. Which is doable. I haven't decided wetheir to try Ron's
On Thu, 11 Sep 2008 23:53:04 +0200, Peter Stuge <[EMAIL PROTECTED]> wrote:
> Joseph Smith wrote:
>> My JMP question is about copying a drives mbr to memory 0x7c00 and
>> or 0x0600 at 512 byte blocks.
> ..
>> What do you think?
>
> I think you should just use SeaBIOS.
>
Nope. This will be a aut
On 11/09/08 17:49 -0400, Joseph Smith wrote:
>
> OK,
> My JMP question is about copying a drives mbr to memory 0x7c00 and or
> 0x0600 at 512 byte
> blocks. Which is doable. I haven't decided wetheir to try Ron's suggestion
> and try to execute the mbr (hence the JMP question) OR we could even writ
Joseph Smith wrote:
> My JMP question is about copying a drives mbr to memory 0x7c00 and
> or 0x0600 at 512 byte blocks.
..
> What do you think?
I think you should just use SeaBIOS.
//Peter
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
OK,
My JMP question is about copying a drives mbr to memory 0x7c00 and or
0x0600 at 512 byte
blocks. Which is doable. I haven't decided wetheir to try Ron's suggestion
and try to execute the mbr (hence the JMP question) OR we could even write
code to translate the mbr and JMP/execute directly to t
Daniel Lindenaar wrote:
yep... I've attached the Makefile.settings file. Please have a look
and see what you think?
regards,
Daniel
OK, tried some other settings, but no dice. Does anybody have a
different idea?
I also get this (note the failed verify):
Disabling local apic...done.
CPU #0
Dear coreboot readers!
This is the automated build check service of coreboot.
The developer "oxygene" checked in revision 3576 to
the coreboot source repository and caused the following
changes:
Change Log:
makes cursorx and cursory signed, as there
are several "if (cursorx < 0)" tests.
I also
Dear coreboot readers!
This is the automated build check service of coreboot.
The developer "jcrouse" checked in revision 3575 to
the coreboot source repository and caused the following
changes:
Change Log:
Fix the USB code to find the headers after they were moved.
Signed-off-by: Jordan Crous
Attached patch updates the FILO in buildrom to the brand new edition.
By IRC concensus, filo-0.5 support has been removed entirely.
--
Jordan Crouse
Systems Software Development Engineer
Advanced Micro Devices, Inc.
[PATCH] libpayload: Update FILO to the trunk
Update FILO to build from the tru
Author: jcrouse
Date: 2008-09-11 21:04:33 +0200 (Thu, 11 Sep 2008)
New Revision: 225
Modified:
buildrom-devel/config/payloads/libpayload-dep.conf
Log:
libpayload: Add the LIBPAYLOAD_PREFIX environment variable for
libpayload aware applications.
Signed-off-by: Jordan Crouse <[EMAIL PROTECTED]>
Author: oxygene
Date: 2008-09-11 20:51:46 +0200 (Thu, 11 Sep 2008)
New Revision: 62
Modified:
trunk/filo/Makefile
Log:
32bit/64bit fixes
Modified: trunk/filo/Makefile
===
--- trunk/filo/Makefile 2008-09-11 18:22:05 UTC (rev 61)
+
Dear coreboot readers!
This is the automated build check service of coreboot.
The developer "jcrouse" checked in revision 3574 to
the coreboot source repository and caused the following
changes:
Change Log:
Move the USB header files to a common location for install
purposes.
Signed-off-by: Jor
Author: oxygene
Date: 2008-09-11 20:22:05 +0200 (Thu, 11 Sep 2008)
New Revision: 61
Modified:
trunk/filo/Makefile
trunk/filo/configs/defconfig
Log:
- add CONFIG_DEBUG_VFS to defconfig
- keep preset CFLAGS alive
Modified: trunk/filo/Makefile
=
The attached patch fixes the unaligned display on serial console that has
occurred due to non-printable characters being inserted on the ramdump and
bootlog screens of coreinfo.
/ulfDo not try to display non-printable characters on the bootlog and
ramdump screens. This fixes unaligned display o
Dear coreboot readers!
This is the automated build check service of coreboot.
The developer "hawke" checked in revision 3573 to
the coreboot source repository and caused the following
changes:
Change Log:
Add the target for the previously-added jetway mainboard.
This target is a copy of the ep
Author: oxygene
Date: 2008-09-11 19:44:45 +0200 (Thu, 11 Sep 2008)
New Revision: 3576
Modified:
trunk/payloads/libpayload/drivers/video/video.c
Log:
makes cursorx and cursory signed, as there
are several "if (cursorx < 0)" tests.
I also added another one, to make backspace
wrap backwards into
On 11/09/08 19:28 +0200, Patrick Georgi wrote:
> Hi,
>
> attached patch makes cursorx and cursory signed, as there are several
> "if (cursorx < 0)" tests.
> I also added another one, to make backspace wrap backwards into the
> previous line, if necessary.
>
Acked-by: Jordan Crouse <[EMAIL PROTEC
Author: jcrouse
Date: 2008-09-11 19:36:40 +0200 (Thu, 11 Sep 2008)
New Revision: 224
Modified:
buildrom-devel/packages/coreinfo/conf/defconfig-coreboot
buildrom-devel/packages/coreinfo/conf/defconfig-coreboot-v3
buildrom-devel/packages/coreinfo/coreinfo.mk
Log:
[PATCH] buildrom: Bump cor
Author: jcrouse
Date: 2008-09-11 19:36:26 +0200 (Thu, 11 Sep 2008)
New Revision: 223
Modified:
buildrom-devel/packages/libpayload/conf/defconfig
buildrom-devel/packages/libpayload/conf/defconfig.geode
buildrom-devel/packages/libpayload/libpayload.mk
Log:
[PATCH] buildrom: Bump libpayload
Author: jcrouse
Date: 2008-09-11 19:36:10 +0200 (Thu, 11 Sep 2008)
New Revision: 222
Modified:
buildrom-devel/scripts/Build.settings
Log:
Export AR for applications that may need it
Signed-off-by: Jordan Crouse <[EMAIL PROTECTED]>
Acked-by: Jordan Crouse <[EMAIL PROTECTED]>
Modified: buildro
Ah, alright. I'll try to test it out on my j7f2 this weekend.
Thanks,
Corey
On Thu, Sep 11, 2008 at 1:12 PM, Alex Mauer <[EMAIL PROTECTED]> wrote:
> Corey Osgood wrote:
>> Doesn't this also need the superio changed to the fintek f71805f?
>
> No, this just the target dir, which references the prev
Patrick Georgi schrieb:
> Hi,
>
> attached patch makes cursorx and cursory signed, as there are several
> "if (cursorx < 0)" tests.
> I also added another one, to make backspace wrap backwards into the
> previous line, if necessary.
>
Oops, forgot this:
Signed-off-by: Patrick Georgi <[EMAIL PRO
Author: jcrouse
Date: 2008-09-11 19:29:00 +0200 (Thu, 11 Sep 2008)
New Revision: 3575
Modified:
trunk/payloads/libpayload/drivers/usb/uhci.c
trunk/payloads/libpayload/drivers/usb/uhci.h
trunk/payloads/libpayload/drivers/usb/usb.c
trunk/payloads/libpayload/drivers/usb/usb_dev.c
trunk
Hi,
attached patch makes cursorx and cursory signed, as there are several
"if (cursorx < 0)" tests.
I also added another one, to make backspace wrap backwards into the
previous line, if necessary.
Patrick Georgi
=== drivers/video/video.c
==
Author: jcrouse
Date: 2008-09-11 19:26:53 +0200 (Thu, 11 Sep 2008)
New Revision: 3574
Added:
trunk/payloads/libpayload/include/usb/
trunk/payloads/libpayload/include/usb/usb.h
trunk/payloads/libpayload/include/usb/usbdisk.h
trunk/payloads/libpayload/include/usb/usbmsc.h
Removed:
tru
Author: hawke
Date: 2008-09-11 19:19:19 +0200 (Thu, 11 Sep 2008)
New Revision: 3573
Added:
trunk/coreboot-v2/targets/jetway/
trunk/coreboot-v2/targets/jetway/j7f24/
trunk/coreboot-v2/targets/jetway/j7f24/Config.lb
Log:
Add the target for the previously-added jetway mainboard.
This target
Corey Osgood wrote:
> Doesn't this also need the superio changed to the fintek f71805f?
No, this just the target dir, which references the previously-created
mainboard dir where the superio was changed.
-Alex Mauer "hawke"
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/
Author: jcrouse
Date: 2008-09-11 19:10:52 +0200 (Thu, 11 Sep 2008)
New Revision: 221
Modified:
buildrom-devel/packages/filo/filo.mk
Log:
The filo repo has moved lately, fix it up and bump the revision to
match.
Signed-off-by: Jordan Crouse <[EMAIL PROTECTED]>
Acked-by: Jordan Crouse <[EMAIL PR
Alex Mauer wrote:
> Attached please find a patch to add a target for the Jetway j7f2 and
> j7f4 motherboard series, corresponding with the previously-added mainboard.
>
> It is a copy of the epia-cn target, with only COREBOOT_EXTRA_VERSION
> changed.
>
> Signed-off-by: Alex Mauer <[EMAIL PROTECTED]
Doesn't this also need the superio changed to the fintek f71805f?
-Corey
On Thu, Sep 11, 2008 at 12:16 PM, ron minnich <[EMAIL PROTECTED]> wrote:
> Acked-by: Ronald G. Minnich <[EMAIL PROTECTED]>
>
> Thanks!
>
> ron
>
> --
> coreboot mailing list: coreboot@coreboot.org
> http://www.coreboot.org/m
Acked-by: Ronald G. Minnich <[EMAIL PROTECTED]>
Thanks!
ron
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Attached please find a patch to add a target for the Jetway j7f2 and
j7f4 motherboard series, corresponding with the previously-added mainboard.
It is a copy of the epia-cn target, with only COREBOOT_EXTRA_VERSION
changed.
Signed-off-by: Alex Mauer <[EMAIL PROTECTED]>
Property changes on: target
ok, here is one more proposal for the eternal pre/post car discussion.
I hope this covers all possibilities.
It will allow all current implementations to remain unchanged, which
is the nice part. But it sets a few simple
rules for the next CPUs, such as core 2.
To recap: At some point stage1 need
On Thu, 11 Sep 2008 15:53:30 +0200, Mats Erik Andersson
<[EMAIL PROTECTED]> wrote:
> Hello Tim,
>
> I copy your original text to the mailing list, in order that you get
> proper credit for the solution I found, based on your comment.
>
>> Hello Mats,
>>
>> Regarding the Coreboot issue, I was w
Wondering if coreboot support is available for my system, if so which
version and special options (if any)? Here's my configuration from
dmidecode:
# dmidecode 2.9
SMBIOS 2.4 present.
34 structures occupying 3234 bytes.
Table at 0x000F.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Hello Tim,
I copy your original text to the mailing list, in order that you get
proper credit for the solution I found, based on your comment.
> Hello Mats,
>
> Regarding the Coreboot issue, I was wondering whether you already had a
> look at the do_ram_command() function in
> src/northbridge/in
Dear coreboot readers!
This is the automated build check service of coreboot.
The developer "stepan" checked in revision 3572 to
the coreboot source repository and caused the following
changes:
Change Log:
>From Vincent Legoll:
Use dev_path() to have nice debug output
patch is run-time tested
69 matches
Mail list logo
