On Tue, Jan 23, 2001 at 05:20:56PM -0600, Steve Shoecraft wrote:
>
> Were you able to get testmod to work?
The problem came from the fact that I was recompiling some of
the pci files. They were locally linked to my module producing
the wrongs results I got.
Sent to -hackers to close the s
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nicolas Souchu
> Sent: Monday, January 22, 2001 10:48 AM
> To: Steve Shoecraft
> Cc: 'John Baldwin'; 'Donald J . Maddox'; [EMAIL PROTECTED]
> Su
On Mon, Jan 22, 2001 at 04:05:31AM -0600, Steve Shoecraft wrote:
> > My viapm driver is a kmodule. Could it be that PCI_READ_CONFIG is not
> > correctly resolved and returns ENXIO which is 0x6?
>
> That's exactly whats going on here. Have you turned on BUS_DEBUG (or mebbe
> DEBUG_BUS) in /kern/s
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Nicolas Souchu
> Sent: Sunday, January 21, 2001 4:19 AM
> To: John Baldwin
> Cc: Donald J . Maddox; [EMAIL PROTECTED]
> Subject: Re: more info about: odd result of pci_read_config
]
> Subject: Re: more info about: odd result of pci_read_config
>
>
> Heh, this is pretty wierd :)
>
> I was intrigued by your little problem, so I started looking around.
> In sys/dev/pci/pciar.h is:
>
> static __inline u_int32_t
> pci_read_config(device_t dev, i
On Sat, Jan 20, 2001 at 04:35:11PM -0800, John Baldwin wrote:
> Look in /sys/compile/ after compiling a kernel, it should be in pci_if.*
> It's a function that ues kobj to lookup the pci_read_config method in the
> parent bus. Look in the PCI code to find the real pci_read_config...
>
> >From s
On Sat, Jan 20, 2001 at 11:11:39PM -0500, Andrew Gallatin wrote:
>
> Nicolas Souchu writes:
> <...>
> > What is the hose field?
>
> It is for server-class alphas. Alphas do their peer PCI buses a
> little differently. Rather than have a ppb between "peer" pci buses,
> each different peer bus
Nicolas Souchu writes:
<...>
> What is the hose field?
It is for server-class alphas. Alphas do their peer PCI buses a
little differently. Rather than have a ppb between "peer" pci buses,
each different peer bus (or hose) is rooted separately at the nexus.
So you can have two PCI buses labele
Thanks for clearing that one up :) I feel a lot better now :)
Now - do you understand why Nicolas' code always returns 0x6? ;-)
On Sat, Jan 20, 2001 at 04:35:11PM -0800, John Baldwin wrote:
> Look in /sys/compile/ after compiling a kernel, it should be in pci_if.*
> It's a function that ues ko
On 21-Jan-01 Donald J . Maddox wrote:
> Heh, this is pretty wierd :)
>
> I was intrigued by your little problem, so I started looking around.
> In sys/dev/pci/pciar.h is:
>
> static __inline u_int32_t
> pci_read_config(device_t dev, int reg, int width)
> {
> return PCI_READ_CONFIG(device_ge
Heh, this is pretty wierd :)
I was intrigued by your little problem, so I started looking around.
In sys/dev/pci/pciar.h is:
static __inline u_int32_t
pci_read_config(device_t dev, int reg, int width)
{
return PCI_READ_CONFIG(device_get_parent(dev), dev, reg, width);
}
However, this is the
11 matches
Mail list logo
