> derive MVME147_SCSI from MVME147 & SCSI
It seems that the preferred semantics would be:
default MVME147_SCSI from MVME147 & SCSI
That way the platform defines sane defaults, but no flexibility has been
taken away.
Presumably many of these defaulted options would also be ones that would
be
derive MVME147_SCSI from MVME147 SCSI
It seems that the preferred semantics would be:
default MVME147_SCSI from MVME147 SCSI
That way the platform defines sane defaults, but no flexibility has been
taken away.
Presumably many of these defaulted options would also be ones that would
be
Miles Lane wrote:
>
> On 19 May 2001 21:06:51 -0400, Benedict Bridgwater wrote:
> > > This bug unconditionally disables a configuration question -- and it's
> > > so old that it has propagated across three port files, without either
> > > of the people who did the cut and paste for the latter
Miles Lane wrote:
On 19 May 2001 21:06:51 -0400, Benedict Bridgwater wrote:
This bug unconditionally disables a configuration question -- and it's
so old that it has propagated across three port files, without either
of the people who did the cut and paste for the latter two noticing
Ben Bridgwater wrote:
> Jeff Garzik wrote:
>
> >
> > Setting DEBUG to 1 in arch/i386/kernel/pci-i386.h gives you lots of
> > info, including PIRQ debug data.
>
> I can try this tonite with 2.4.4 if this is going to be useful.
>
Well, I don't know how useful this
Ben Bridgwater wrote:
Jeff Garzik wrote:
Setting DEBUG to 1 in arch/i386/kernel/pci-i386.h gives you lots of
info, including PIRQ debug data.
I can try this tonite with 2.4.4 if this is going to be useful.
Well, I don't know how useful this is going to be, since the kernel booted
6 matches
Mail list logo
