Thus spake Kenneth Wayne Culver ([EMAIL PROTECTED]):
> SYS_RES_MEMORY instead of SYS_RES_IOPORT (all these combinations are for
> use in bus_alloc_resource). The thing is everything I've tried fails to
> work, so I can't attach my driver because it won't map the resources.
> Can anyone suggest ot
I havn't checked, but I'll probably do that soon.
Ken
On Wed, 25 Jul 2001 [EMAIL PROTECTED] wrote:
>
>
> On Wed, 25 Jul 2001, Kenneth Wayne Culver wrote:
>
> > Well, I could do that, but I'd rather write a complete driver with all the
> > regular interfaces... (open, close, ioctl, and a spec
On Wed, 25 Jul 2001, Kenneth Wayne Culver wrote:
> Well, I could do that, but I'd rather write a complete driver with all the
> regular interfaces... (open, close, ioctl, and a specific major/minor in
> the kernel, I'm going to add other chips to this driver eventually) The
> way you are sugges
Well, I could do that, but I'd rather write a complete driver with all the
regular interfaces... (open, close, ioctl, and a specific major/minor in
the kernel, I'm going to add other chips to this driver eventually) The
way you are suggesting just opens /dev/io and uses inb and outb to do some
hac
On Wed, 25 Jul 2001, Kenneth Wayne Culver wrote:
> Sorry to post to this forum, but I'm not getting any replies from -hackers
> or -questions, and I've looked at the webpages on writing device drivers,
> as well as several other drivers. Here's my problem/question/whatever...
>
> I am writing
Sorry to post to this forum, but I'm not getting any replies from -hackers
or -questions, and I've looked at the webpages on writing device drivers,
as well as several other drivers. Here's my problem/question/whatever...
I am writing a driver right now for the Hardware monitoring features of
the
