New wpi driver

[Attilio Rao]

2006/11/10, Attilio Rao <attilio at freebsd.org>:
> 2006/11/10, Attilio Rao <attilio at freebsd.org>:
> > 2006/11/10, Max Laier <max at love2party.net>:
> > > On Friday 10 November 2006 10:37, Massimo Lusetti wrote:
> > > > On Thu, 2006-11-09 at 22:39 +0100, Gábor Kövesdán wrote:
> > > > > Unfortunately, it seems that this is still that unfinished driver from
> > > > > Damien, that circulates on the net everywhere, but it only works for
> > > > > some lucky people. As for me, I get an error message when loading the
> > > > > module, that it could not allocate resources.
> > > >
> > > > I don't think it's "that unfinished driver from Damien" classify it
> > > > correctly, as stated it's an unsupported version so case where it will
> > > > not work are expected. Feel free to improve it or wait when some FreeBSD
> > > > developer will port and maintain it.
> > >
> > > I agree.  On top of that, a more detailed error report would be preferable.
> > > From what you put above, it seems that you are out of sufficient continous
> > > memory at the point where you enable the hardware.  Try enabling it before
> > > bringing up X11 etc.
> >
> > Even if I'm not totally aware about what problem are gabor@ is having
> > at the moment, some time ago I started looking at the code and one
> > difference between ipi and wpi is in rings they use (and their
> > allocation) and again in the usage of a shared DMA memory page between
> > the host and the NIC.
>
> s/ipi/iwi.

Ok I gave a quick look at the code and gabor@ problem is about
memory-mapped I/O resource allocation.

First of all, WPI_PCI_BAR0 might not be defined in this way, but it
should really use PCIR_BAR() macro.
Then, probabilly, gabor's device I/O space is relative to another BAR,
so simply try all 6 using PCIR_BAR(n) where n range is 0-6 until it
does allocate.

Attilio

PS: I would like that the code will better follow stlye(9) too...

-- 
Peace can only be achieved by understanding - A. Einstein