See patch
On Tue, 24 Mar 2009 12:41:15 +0100, Stefan Reinauer stepan@coresystems.de wrote:
See patch
This may be trivial, but in case not Acked-by: Joseph Smith joe@settoplinux.org
Stefan Reinauer wrote:
Every object file with a struct pci_driver ... __pci_driver needs to be marked as "driver" instead of "object" in order to get the init code actually executed.
This patch fixes up all northbridges that did not do this before.
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Acked-by: Peter Stuge peter@stuge.se
How come we have not noticed this before? Do these NB drivers not do anything critical?
//Peter
On Tue, Mar 24, 2009 at 12:06 PM, Peter Stuge peter@stuge.se wrote:
Stefan Reinauer wrote:
Every object file with a struct pci_driver ... __pci_driver needs to be marked as "driver" instead of "object" in order to get the init code actually executed.
This patch fixes up all northbridges that did not do this before.
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Acked-by: Peter Stuge peter@stuge.se
How come we have not noticed this before? Do these NB drivers not do anything critical?
Please hold off until tomorrow on committing this. IIRC I tried this with cn700 and something broke, but I don't remember what or why.
Thanks, Corey
Corey Osgood wrote:
Please hold off until tomorrow on committing this. IIRC I tried this with cn700 and something broke, but I don't remember what or why.
It's already in now, but can be reverted of course. It's an interesting bug..
//Peter
On Tue, 24 Mar 2009 17:17:50 +0100, Peter Stuge peter@stuge.se wrote:
Corey Osgood wrote:
Please hold off until tomorrow on committing this. IIRC I tried this with cn700 and something broke, but I don't remember what or why.
It's already in now, but can be reverted of course. It's an interesting bug..
I don't think it is a good idea to revert if cn700 is the only one broken. I have tested the i82830 and it works fine. For the fist time I can see "Northbridge init", not that it does anything but it is nice to know the code is working now, just in case I need to do something with it in the future. Maybe another patch switching cn700 back if confirmed it is broken?
On Tue, Mar 24, 2009 at 3:24 PM, Joseph Smith joe@settoplinux.org wrote:
On Tue, 24 Mar 2009 17:17:50 +0100, Peter Stuge peter@stuge.se wrote:
Corey Osgood wrote:
Please hold off until tomorrow on committing this. IIRC I tried this with cn700 and something broke, but I don't remember what or why.
It's already in now, but can be reverted of course. It's an interesting bug..
I don't think it is a good idea to revert if cn700 is the only one broken. I have tested the i82830 and it works fine. For the fist time I can see "Northbridge init", not that it does anything but it is nice to know the code is working now, just in case I need to do something with it in the future. Maybe another patch switching cn700 back if confirmed it is broken?
It doesn't break abuild. If something does break, it's probably a problem with the code and not the config, I'll fix it this weekend if that's the case.
-Corey
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of Peter Stuge Sent: Tuesday, March 24, 2009 10:06 AM To: coreboot@coreboot.org Subject: Re: [coreboot] [PATCH] fix object/driver confusion ofall northbridge code
Stefan Reinauer wrote:
Every object file with a struct pci_driver ... __pci_driver needs to be marked as "driver" instead of "object" in order to get the init code actually executed.
This patch fixes up all northbridges that did not do this before.
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Acked-by: Peter Stuge peter@stuge.se
How come we have not noticed this before? Do these NB drivers not do anything critical?
It is hard to believe that the amdk8 northbridge code never got executed. Is this only true if it's not contained in a "chip", or if you don't specify its position in the device tree?
Thanks, Myles
On Tue, Mar 24, 2009 at 12:32 PM, Myles Watson mylesgw@gmail.com wrote:
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:
coreboot-bounces@coreboot.org]
On Behalf Of Peter Stuge Sent: Tuesday, March 24, 2009 10:06 AM To: coreboot@coreboot.org Subject: Re: [coreboot] [PATCH] fix object/driver confusion ofall northbridge code
Stefan Reinauer wrote:
Every object file with a struct pci_driver ... __pci_driver needs to be marked as "driver" instead of "object" in order to get the init code actually executed.
This patch fixes up all northbridges that did not do this before.
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Acked-by: Peter Stuge peter@stuge.se
How come we have not noticed this before? Do these NB drivers not do anything critical?
It is hard to believe that the amdk8 northbridge code never got executed. Is this only true if it's not contained in a "chip", or if you don't specify its position in the device tree?
I'm grasping at straws, but I think it had something to do with multiple drivers in northbridge.c, if it's marked as a driver only the first driver would get run, or it might have been something to do with the special pci domain and cpu bus drivers. Then again, I could be entirely wrong, it's been a while.
-Corey
On Tue, 24 Mar 2009 12:53:53 -0400, Corey Osgood corey.osgood@gmail.com wrote:
On Tue, Mar 24, 2009 at 12:32 PM, Myles Watson mylesgw@gmail.com wrote:
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:
coreboot-bounces@coreboot.org]
On Behalf Of Peter Stuge Sent: Tuesday, March 24, 2009 10:06 AM To: coreboot@coreboot.org Subject: Re: [coreboot] [PATCH] fix object/driver confusion ofall northbridge code
Stefan Reinauer wrote:
Every object file with a struct pci_driver ... __pci_driver needs to be marked as "driver" instead of "object" in order to get the init code actually executed.
This patch fixes up all northbridges that did not do this before.
Signed-off-by: Stefan Reinauer stepan@coresystems.de
Acked-by: Peter Stuge peter@stuge.se
How come we have not noticed this before? Do these NB drivers not do anything critical?
It is hard to believe that the amdk8 northbridge code never got
executed.
Is this only true if it's not contained in a "chip", or if you don't specify its position in the device tree?
I'm grasping at straws, but I think it had something to do with multiple drivers in northbridge.c, if it's marked as a driver only the first
driver
would get run, or it might have been something to do with the special pci domain and cpu bus drivers. Then again, I could be entirely wrong, it's been a while.
I don't have access right now, can someone do a abuild?