Any devices using the ppbus will end up sharing the hardware port. If i want
to access this resource info, should i store it in my local driver's softc
structure, or extract it from the parent device (ppbus)?
jcm
--
"I drank WHAT ?!" - Socrates
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
Thus spake j mckitrick ([EMAIL PROTECTED]):
> Any devices using the ppbus will end up sharing the hardware port. If i want
> to access this resource info, should i store it in my local driver's softc
> structure, or extract it from the parent device (ppbus)?
What about bus_alloc_resource()?
Or
On Thu, May 24, 2001 at 11:38:15AM +0200, Alexander Langer wrote:
| Thus spake j mckitrick ([EMAIL PROTECTED]):
|
| > Any devices using the ppbus will end up sharing the hardware port. If i want
| > to access this resource info, should i store it in my local driver's softc
| > structure, or extr
In message <[EMAIL PROTECTED]> j mckitrick writes:
: Any devices using the ppbus will end up sharing the hardware port. If i want
: to access this resource info, should i store it in my local driver's softc
: structure, or extract it from the parent device (ppbus)?
There should be a method for g
In message <[EMAIL PROTECTED]> j mckitrick writes:
: Well, all of the resources have already been allocated when the ppc device
: has been attached. The hardware port and interrupt have already been
: reserved and stored in the softc data structure for ppc. All devices
: attached to ppc, like pp
5 matches
Mail list logo