| Submitter | Myles Watson |
|---|---|
| Date | 2009-10-01 16:04:54 |
| Message ID | <2831fecf0910010904t7b609492t7e77b5fa0d5cca21@mail.gmail.com> |
| Download | mbox | patch |
| Permalink | /patch/316/ |
| State | Accepted |
| Headers | show |
Comments
That patch looks fine to me, is there an issue? ron
On Thu, Oct 1, 2009 at 10:14 AM, ron minnich <rminnich@gmail.com> wrote: > That patch looks fine to me, is there an issue? Not that I know of. It was just waiting for review. I just forgot to include my sign off with the updated patch. Signed-off-by: Myles Watson <mylesgw@gmail.com> Thanks, Myles
On Thu, Oct 1, 2009 at 9:17 AM, Myles Watson <mylesgw@gmail.com> wrote: > On Thu, Oct 1, 2009 at 10:14 AM, ron minnich <rminnich@gmail.com> wrote: >> That patch looks fine to me, is there an issue? > Not that I know of. It was just waiting for review. I just forgot to > include my sign off with the updated patch. > > Signed-off-by: Myles Watson <mylesgw@gmail.com> Acked-by: Ronald G. Minnich <rminnich@gmail.com>
On Thu, Oct 1, 2009 at 10:19 AM, ron minnich <rminnich@gmail.com> wrote: > On Thu, Oct 1, 2009 at 9:17 AM, Myles Watson <mylesgw@gmail.com> wrote: >> On Thu, Oct 1, 2009 at 10:14 AM, ron minnich <rminnich@gmail.com> wrote: >>> That patch looks fine to me, is there an issue? >> Not that I know of. It was just waiting for review. I just forgot to >> include my sign off with the updated patch. >> >> Signed-off-by: Myles Watson <mylesgw@gmail.com> > > Acked-by: Ronald G. Minnich <rminnich@gmail.com> Rev 4702. Thanks, Myles
Thanks. I took option number 2. It flashed successfully, however, gpxe
does not seem to be starting. Here is the output from the coreboot/seabios:
coreboot-2.0.0-r_s2881_Fallback Thu Oct 1 17:07:49 MDT 2009 starting...
(0,1) link=00
(1,0) link=00
02 nodes initialized.
core0 started: 01
started ap apicid:
SBLink=02
NC node|link=02
ht reset -
coreboot-2.0.0-r_s2881_Fallback Thu Oct 1 17:07:49 MDT 2009 starting...
(0,1) link=00
(1,0) link=00
02 nodes initialized.
core0 started: 01
started ap apicid:
SBLink=02
NC node|link=02
Ram1.00
Ram1.01
Ram2.00
RAM end at 0x00100000 kB
Ram2.01
RAM end at 0x00200000 kB
Ram3
Initializing memory: done
Initializing memory: done
Ram4
v_esp=000cfe38
testx = 5a5a5a5a
Copying data from cache to RAM -- switching to use RAM as stack... Done
testx = 5a5a5a5a
Disabling cache as ram now
Clearing initial memory region: Done
Jumping to image.
Check fallback/payload
Check fallback/coreboot_ram
Stage: load fallback/coreboot_ram @ 16384/245760 bytes, enter @ 4000
Stage: done loading.
Jumping to image.
coreboot-2.0.0-r_s2881_Fallback Thu Oct 1 17:07:49 MDT 2009 booting...
Enumerating buses...
Show all devs...Before Device Enumeration.
Root Device: enabled 1, 0 resources
APIC_CLUSTER: 0: enabled 1, 0 resources
APIC: 00: enabled 1, 0 resources
PCI_DOMAIN: 0000: enabled 1, 0 resources
PCI: 00:18.0: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:09.0: enabled 1, 0 resources
PCI: 00:09.1: enabled 1, 0 resources
PCI: 00:0a.0: enabled 1, 0 resources
PCI: 00:0a.1: enabled 1, 0 resources
PCI: 00:00.1: enabled 1, 0 resources
PCI: 00:01.0: enabled 1, 0 resources
PCI: 00:01.1: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:00.1: enabled 1, 0 resources
PCI: 00:00.2: enabled 0, 0 resources
PCI: 00:01.0: enabled 0, 0 resources
PCI: 00:05.0: enabled 1, 0 resources
PCI: 00:06.0: enabled 1, 0 resources
PCI: 00:01.0: enabled 1, 0 resources
PNP: 002e.0: enabled 1, 3 resources
PNP: 002e.1: enabled 0, 2 resources
PNP: 002e.2: enabled 1, 2 resources
PNP: 002e.3: enabled 0, 2 resources
PNP: 002e.5: enabled 1, 4 resources
PNP: 002e.6: enabled 0, 1 resources
PNP: 002e.7: enabled 0, 3 resources
PNP: 002e.8: enabled 0, 0 resources
PNP: 002e.9: enabled 0, 0 resources
PNP: 002e.a: enabled 0, 0 resources
PNP: 002e.b: enabled 1, 2 resources
PCI: 00:01.1: enabled 1, 0 resources
PCI: 00:01.2: enabled 1, 0 resources
PCI: 00:01.3: enabled 1, 0 resources
I2C: 00:50: enabled 1, 0 resources
I2C: 00:51: enabled 1, 0 resources
I2C: 00:52: enabled 1, 0 resources
I2C: 00:53: enabled 1, 0 resources
I2C: 00:54: enabled 1, 0 resources
I2C: 00:55: enabled 1, 0 resources
I2C: 00:56: enabled 1, 0 resources
I2C: 00:57: enabled 1, 0 resources
I2C: 00:2d: enabled 1, 0 resources
I2C: 00:2a: enabled 1, 0 resources
I2C: 00:49: enabled 1, 0 resources
I2C: 00:4a: enabled 1, 0 resources
PCI: 00:01.5: enabled 0, 0 resources
PCI: 00:01.6: enabled 0, 0 resources
PCI: 00:18.1: enabled 1, 0 resources
PCI: 00:18.2: enabled 1, 0 resources
PCI: 00:18.3: enabled 1, 0 resources
Compare with tree...
Root Device: enabled 1, 0 resources
APIC_CLUSTER: 0: enabled 1, 0 resources
APIC: 00: enabled 1, 0 resources
PCI_DOMAIN: 0000: enabled 1, 0 resources
PCI: 00:18.0: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:09.0: enabled 1, 0 resources
PCI: 00:09.1: enabled 1, 0 resources
PCI: 00:0a.0: enabled 1, 0 resources
PCI: 00:0a.1: enabled 1, 0 resources
PCI: 00:00.1: enabled 1, 0 resources
PCI: 00:01.0: enabled 1, 0 resources
PCI: 00:01.1: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:00.0: enabled 1, 0 resources
PCI: 00:00.1: enabled 1, 0 resources
PCI: 00:00.2: enabled 0, 0 resources
PCI: 00:01.0: enabled 0, 0 resources
PCI: 00:05.0: enabled 1, 0 resources
PCI: 00:06.0: enabled 1, 0 resources
PCI: 00:01.0: enabled 1, 0 resources
PNP: 002e.0: enabled 1, 3 resources
PNP: 002e.1: enabled 0, 2 resources
PNP: 002e.2: enabled 1, 2 resources
PNP: 002e.3: enabled 0, 2 resources
PNP: 002e.5: enabled 1, 4 resources
PNP: 002e.6: enabled 0, 1 resources
PNP: 002e.7: enabled 0, 3 resources
PNP: 002e.8: enabled 0, 0 resources
PNP: 002e.9: enabled 0, 0 resources
PNP: 002e.a: enabled 0, 0 resources
PNP: 002e.b: enabled 1, 2 resources
PCI: 00:01.1: enabled 1, 0 resources
PCI: 00:01.2: enabled 1, 0 resources
PCI: 00:01.3: enabled 1, 0 resources
I2C: 00:50: enabled 1, 0 resources
I2C: 00:51: enabled 1, 0 resources
I2C: 00:52: enabled 1, 0 resources
I2C: 00:53: enabled 1, 0 resources
I2C: 00:54: enabled 1, 0 resources
I2C: 00:55: enabled 1, 0 resources
I2C: 00:56: enabled 1, 0 resources
I2C: 00:57: enabled 1, 0 resources
I2C: 00:2d: enabled 1, 0 resources
I2C: 00:2a: enabled 1, 0 resources
I2C: 00:49: enabled 1, 0 resources
I2C: 00:4a: enabled 1, 0 resources
PCI: 00:01.5: enabled 0, 0 resources
PCI: 00:01.6: enabled 0, 0 resources
PCI: 00:18.1: enabled 1, 0 resources
PCI: 00:18.2: enabled 1, 0 resources
PCI: 00:18.3: enabled 1, 0 resources
APIC_CLUSTER: 0 enabled
PCI_DOMAIN: 0000 enabled
PCI: 00:18.3 siblings=0
CPU: APIC: 00 enabled
PCI: 00:19.0 [1022/1100] enabled
PCI: 00:19.1 [1022/1101] enabled
PCI: 00:19.2 [1022/1102] enabled
PCI: 00:19.3 [1022/1103] enabled
PCI: 00:19.3 siblings=0
CPU: APIC: 01 enabled
PCI: pci_scan_bus for bus 00
PCI: 00:18.0 [1022/1100] enabled
PCI: 00:18.1 [1022/1101] enabled
PCI: 00:18.2 [1022/1102] enabled
PCI: 00:18.3 [1022/1103] enabled
PCI: 00:19.0 [1022/1100] enabled
PCI: 00:19.1 [1022/1101] enabled
PCI: 00:19.2 [1022/1102] enabled
PCI: 00:19.3 [1022/1103] enabled
I don't see 14e4/1648 above. Is that the problem? Any suggestions?
Thanks.
> Thanks. I took option number 2. It flashed successfully, however, gpxe > does not seem to be starting. Here is the output from the > coreboot/seabios: > PCI: 00:01.5: enabled 0, 0 resources > PCI: 00:01.6: enabled 0, 0 resources > PCI: 00:18.1: enabled 1, 0 resources > PCI: 00:18.2: enabled 1, 0 resources > PCI: 00:18.3: enabled 1, 0 resources > APIC_CLUSTER: 0 enabled > PCI_DOMAIN: 0000 enabled > PCI: 00:18.3 siblings=0 > CPU: APIC: 00 enabled > PCI: 00:19.0 [1022/1100] enabled > PCI: 00:19.1 [1022/1101] enabled > PCI: 00:19.2 [1022/1102] enabled > PCI: 00:19.3 [1022/1103] enabled > PCI: 00:19.3 siblings=0 > CPU: APIC: 01 enabled > PCI: pci_scan_bus for bus 00 > PCI: 00:18.0 [1022/1100] enabled > PCI: 00:18.1 [1022/1101] enabled > PCI: 00:18.2 [1022/1102] enabled > PCI: 00:18.3 [1022/1103] enabled > PCI: 00:19.0 [1022/1100] enabled > PCI: 00:19.1 [1022/1101] enabled > PCI: 00:19.2 [1022/1102] enabled > PCI: 00:19.3 [1022/1103] enabled > > I don't see 14e4/1648 above. Is that the problem? It should come after this. The full log would be helpful. Do you see the device's PCI device number that you see in lspci? eg. PCI: 00:01.5 Thanks, Myles
This is all the output I get on the serial port. How can I get a full log? I do not see the device number, its: 02:09.0 .
looking better. Did I miss something? I don't see seabios in there. ron
> -----Original Message----- > From: Hugh Greenberg [mailto:hng@lanl.gov] > Sent: Thursday, October 01, 2009 5:46 PM > To: Myles Watson > Cc: coreboot@coreboot.org > Subject: Re: [coreboot] tyan s2881 with seabios and gpxe > > This is all the output I get on the serial port. How can I get a full > log? I do not see the device number, its: 02:09.0 . I thought you'd truncated it. It's hanging for some reason. I've never seen Coreboot hang there. > > -- > Hugh Greenberg > Los Alamos National Laboratory, CCS-1 > Email: hng@lanl.gov > Phone: (505) 665-6471 > > > > Myles Watson wrote: > >> Thanks. I took option number 2. It flashed successfully, however, > gpxe > >> does not seem to be starting. Here is the output from the > >> coreboot/seabios: > >> > > > > > >> PCI: 00:01.5: enabled 0, 0 resources > >> PCI: 00:01.6: enabled 0, 0 resources > >> PCI: 00:18.1: enabled 1, 0 resources > >> PCI: 00:18.2: enabled 1, 0 resources > >> PCI: 00:18.3: enabled 1, 0 resources > >> APIC_CLUSTER: 0 enabled > >> PCI_DOMAIN: 0000 enabled > >> PCI: 00:18.3 siblings=0 > >> CPU: APIC: 00 enabled > >> PCI: 00:19.0 [1022/1100] enabled > >> PCI: 00:19.1 [1022/1101] enabled > >> PCI: 00:19.2 [1022/1102] enabled > >> PCI: 00:19.3 [1022/1103] enabled > >> PCI: 00:19.3 siblings=0 > >> CPU: APIC: 01 enabled > >> PCI: pci_scan_bus for bus 00 > >> PCI: 00:18.0 [1022/1100] enabled > >> PCI: 00:18.1 [1022/1101] enabled > >> PCI: 00:18.2 [1022/1102] enabled > >> PCI: 00:18.3 [1022/1103] enabled > >> PCI: 00:19.0 [1022/1100] enabled > >> PCI: 00:19.1 [1022/1101] enabled > >> PCI: 00:19.2 [1022/1102] enabled > >> PCI: 00:19.3 [1022/1103] enabled > >> > >> I don't see 14e4/1648 above. Is that the problem? > >> > > It should come after this. The full log would be helpful. Do you see > the > > device's PCI device number that you see in lspci? eg. PCI: 00:01.5 The next thing in my log is: PCI: Using configuration type 1 Do you want to try Rev 4645? 4646 was the last one that touched that code. Sorry I'm not more help. Thanks, Myles
> This is all the output I get on the serial port. How can I get a full > log? If you set CONFIG_DEFAULT_CONSOLE_LOGLEVEL = 9 CONFIG_MAXIMUM_CONSOLE_LOGLEVEL = 9 You may get some more useful information. Thanks, Myles
I was able to get coreboot pretty much up and running with gpxe and seabios. The trick was to use the Kconfig build system instead. I still have an issue though. I was not able to build it with ACPI tables, an mp table, or a PIRQ table. If I did, I got this error: make: *** No rule to make target `/local/coreboot-v2/src/mainboard/tyan/s2881/dsdt.dsl', needed by `/local/coreboot-v2/build/dsdt.c'. Stop. It seems as though I need these tables as Linux is not able to load the drivers for any PCI device. Could someone help me with this? Thanks again.
On Wed, Oct 7, 2009 at 2:14 PM, Hugh Greenberg <hng@lanl.gov> wrote: > I was able to get coreboot pretty much up and running with gpxe and seabios. > The trick was to use the Kconfig build system instead. I still have an > issue though. I was not able to build it with ACPI tables, an mp table, or > a PIRQ table. If I did, I got this error: > > make: *** No rule to make target > `/local/coreboot-v2/src/mainboard/tyan/s2881/dsdt.dsl', needed by > `/local/coreboot-v2/build/dsdt.c'. Stop. The Tyan s2881 doesn't have ACPI support. It compiles for me if I select Generate an MP table & Generate a PIRQ table Could you try selecting just those two in the System Tables menu? Thanks, Myles
Yeah, it compiled. Thanks.
Myles Watson wrote:
> The Tyan s2881 doesn't have ACPI support.
Each board should indicate this, so that the menu does not show
options which are known to not work.
//Peter
On Wed, Oct 7, 2009 at 4:46 PM, Peter Stuge <peter@stuge.se> wrote: > Myles Watson wrote: >> The Tyan s2881 doesn't have ACPI support. > > Each board should indicate this, so that the menu does not show > options which are known to not work. Absolutely agreed. I think there will have to be another variable like HAS_ACPI_SUPPORT for that to happen. Right now HAVE_ACPI_TABLES defaults to 'n' in the s2881. Is there another way? Thanks, Myles
Myles Watson wrote: > >> The Tyan s2881 doesn't have ACPI support. > > > > Each board should indicate this, so that the menu does not show > > options which are known to not work. > > Absolutely agreed. I think there will have to be another variable > like HAS_ACPI_SUPPORT for that to happen. How about simply ACPI? > Right now HAVE_ACPI_TABLES defaults to 'n' in the s2881. > > Is there another way? I don't think so, but I think it's fine to add CONFIG_ACPI for this. //Peter
On Wed, Oct 7, 2009 at 5:02 PM, Peter Stuge <peter@stuge.se> wrote: > Myles Watson wrote: >> Absolutely agreed. I think there will have to be another variable >> like HAS_ACPI_SUPPORT for that to happen. > > How about simply ACPI? I think HAVE_ACPI_TABLES should become GENERATE_ACPI_TABLES and HAVE_ACPI_TABLES should take that new meaning. ACPI isn't specific enough to see what it does without looking elsewhere. >> Right now HAVE_ACPI_TABLES defaults to 'n' in the s2881. >> >> Is there another way? > > I don't think so, but I think it's fine to add CONFIG_ACPI for this. Great. As soon as all boards have Kconfig support I think that should be done. Thanks, Myles
Myles Watson wrote: > >> Absolutely agreed. I think there will have to be another variable > >> like HAS_ACPI_SUPPORT for that to happen. > > > > How about simply ACPI? > > I think HAVE_ACPI_TABLES should become GENERATE_ACPI_TABLES I like that! > and HAVE_ACPI_TABLES should take that new meaning. ACPI isn't > specific enough to see what it does without looking elsewhere. All right. By the way - maybe we too should store big static tables in cbfs? //Peter
> By the way - maybe we too should store big static tables in cbfs?
I'm don't think ACPI is static enough. On my board the DSDT (3K) is
the only static one. I'm not sure it's worth the trouble. I could be
proven wrong.
Thanks,
Myles
Myles Watson wrote: >> By the way - maybe we too should store big static tables in cbfs? >> > I'm don't think ACPI is static enough. On my board the DSDT (3K) is > the only static one. I'm not sure it's worth the trouble. I could be > proven wrong. > I agree with you,.. it's not a big win either. Stefan
Patch
Index: svn/src/cpu/amd/model_fxx/Kconfig =================================================================== --- svn.orig/src/cpu/amd/model_fxx/Kconfig +++ svn/src/cpu/amd/model_fxx/Kconfig @@ -1,3 +1,7 @@ +config CPU_AMD_MODEL_FXX + bool + default n + config HAVE_INIT_TIMER bool default y Index: svn/src/northbridge/amd/amdk8/Kconfig =================================================================== --- svn.orig/src/northbridge/amd/amdk8/Kconfig +++ svn/src/northbridge/amd/amdk8/Kconfig @@ -27,6 +27,11 @@ config AGP_APERTURE_SIZE default 0x4000000 depends on NORTHBRIDGE_AMD_AMDK8 +config K8_HT_FREQ_1G_SUPPORT + bool + default n + depends on NORTHBRIDGE_AMD_AMDK8 + config HYPERTRANSPORT_PLUGIN_SUPPORT bool default y Index: svn/src/cpu/Kconfig =================================================================== --- svn.orig/src/cpu/Kconfig +++ svn/src/cpu/Kconfig @@ -25,7 +25,3 @@ config SMP bool default y if MAX_CPUS != 1 default n - -config CPU_SOCKET_TYPE - hex - default 0 Index: svn/src/cpu/amd/socket_AM2/Kconfig =================================================================== --- svn.orig/src/cpu/amd/socket_AM2/Kconfig +++ svn/src/cpu/amd/socket_AM2/Kconfig @@ -4,6 +4,7 @@ config CPU_AMD_SOCKET_AM2 select K8_REV_F_SUPPORT # Opteron K8 1G HT support select K8_HT_FREQ_1G_SUPPORT + select CPU_AMD_MODEL_FXX config CPU_SOCKET_TYPE hex Index: svn/src/cpu/amd/socket_F/Kconfig =================================================================== --- svn.orig/src/cpu/amd/socket_F/Kconfig +++ svn/src/cpu/amd/socket_F/Kconfig @@ -2,8 +2,8 @@ config CPU_AMD_SOCKET_F bool default n select K8_REV_F_SUPPORT - # Opteron K8 1G HT support select K8_HT_FREQ_1G_SUPPORT + select CPU_AMD_MODEL_FXX config CPU_SOCKET_TYPE hex Index: svn/src/cpu/amd/socket_S1G1/Kconfig =================================================================== --- svn.orig/src/cpu/amd/socket_S1G1/Kconfig +++ svn/src/cpu/amd/socket_S1G1/Kconfig @@ -3,6 +3,7 @@ config CPU_AMD_SOCKET_S1G1 default n select K8_REV_F_SUPPORT select K8_HT_FREQ_1G_SUPPORT + select CPU_AMD_MODEL_FXX config CPU_SOCKET_TYPE hex Index: svn/src/cpu/amd/Kconfig =================================================================== --- svn.orig/src/cpu/amd/Kconfig +++ svn/src/cpu/amd/Kconfig @@ -1,3 +1,7 @@ +config K8_REV_F_SUPPORT + bool + default n + #source src/cpu/amd/socket_754/Kconfig #source src/cpu/amd/socket_939/Kconfig source src/cpu/amd/socket_940/Kconfig Index: svn/src/cpu/amd/socket_940/Kconfig =================================================================== --- svn.orig/src/cpu/amd/socket_940/Kconfig +++ svn/src/cpu/amd/socket_940/Kconfig @@ -1,11 +1,10 @@ config CPU_AMD_SOCKET_940 bool default n - #Opteron K8 1G HT Support select K8_HT_FREQ_1G_SUPPORT select CPU_AMD_MODEL_FXX -config K8_REV_F_SUPPORT - bool - default n +config CPU_SOCKET_TYPE + hex + default 0x0 depends on CPU_AMD_SOCKET_940