On Thu, Jun 05, 2003 at 04:17:38AM -0700, Terry Lambert wrote:
> How about RF_DONTCHECK or RF_ALWAYSWORKS? It better implies
> what's happening here, since you're going to assume success in
> the face of diagnostics to the contrary.
>
> So instead of:
>
> if (flag)
> return (
"David P. Reese Jr." wrote:
> > > A snip of code from sys/dev/pci/pci.c:pci_enable_io_method():
> > >
> > > pci_set_command_bit(dev, child, bit);
> > > command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2);
> > > if (command & bit)
> > > return (0);
> > >
On Wed, Jun 04, 2003 at 07:29:31AM +, Nicolas Souchu wrote:
> On Tue, Jun 03, 2003 at 10:54:30AM -0700, David P. Reese Jr. wrote:
>
> [...]
> > : The datasheet states that the command bits are RW but "fixed at 0".
> >
> > A snip of code from sys/dev/pci/pci.c:pci_enable_io_method():
> >
> >
On Tue, Jun 03, 2003 at 10:54:30AM -0700, David P. Reese Jr. wrote:
[...]
> : The datasheet states that the command bits are RW but "fixed at 0".
>
> A snip of code from sys/dev/pci/pci.c:pci_enable_io_method():
>
> pci_set_command_bit(dev, child, bit);
> command = PCI_READ_CONFI
On Tue, Jun 03, 2003 at 01:54:36AM -0500, Conrad Sabatier wrote:
>
> On 02-Jun-2003 Nicolas Souchu wrote:
> > On Sun, Jun 01, 2003 at 01:52:57AM +0200, Dag-Erling Smorgrav wrote:
> >>
> >> viapropm is seriously broken for other reasons and needs professional
> >> help.
> >
> > What kind of break
On 02-Jun-2003 Nicolas Souchu wrote:
> On Sun, Jun 01, 2003 at 01:52:57AM +0200, Dag-Erling Smorgrav wrote:
>>
>> viapropm is seriously broken for other reasons and needs professional
>> help.
>
> What kind of breakage? Setting resources in probe? Right. Anybody having
> the viapm driver loaded
On Sun, Jun 01, 2003 at 01:52:57AM +0200, Dag-Erling Smorgrav wrote:
> "David P. Reese Jr." <[EMAIL PROTECTED]> writes:
> > In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a
> > pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG
> > and comparing the results. For
On Sun, Jun 01, 2003 at 01:52:57AM +0200, Dag-Erling Smorgrav wrote:
> "David P. Reese Jr." <[EMAIL PROTECTED]> writes:
> > In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a
> > pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG
> > and comparing the results. For
"David P. Reese Jr." <[EMAIL PROTECTED]> writes:
> In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a
> pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG
> and comparing the results. For some odd reason, this doesnt work when
> my viapropm tries to attach.
viapr
In message: <[EMAIL PROTECTED]>
"David P. Reese Jr." <[EMAIL PROTECTED]> writes:
: Is it my chipset's fault for not reading back the correct register value?
: The board is a SOYO K7VTAPRO-2AA6. What other info would be helpful in
: this situation?
It appears that there's some non-zero
In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a
pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG
and comparing the results. For some odd reason, this doesnt work when
my viapropm tries to attach. Allocating its port resources fails in
pci_enable_io_method().
11 matches
Mail list logo