public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kathy Frazier" <kfrazier@daetwyler-rd.com>
To: "'Miguel Ojeda'" <miguel.ojeda.sandonis@gmail.com>,
	"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: "'Kathy Frazier'" <kfrazier@daetwyler-rd.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: Talking to parallel port in 2.6 kernel without using parport
Date: Mon, 28 Apr 2008 14:06:20 -0400	[thread overview]
Message-ID: <004301c8a95a$906666c0$b1333440$@com> (raw)
In-Reply-To: <ca2dc2820804251118j625abb76j100d165aee18a7c8@mail.gmail.com>

Miguel,

Thanks for your response!  I took a look at ks0108.c.  You are right:  very
straightforward and a good reference.  I had added some other things based
on what I saw in /drivers/char/ppdev.c, lp.c and tipar.c.  After reviewing
yours, I am realizing I really don't need some of that, so I can simplify
mine.

My biggest problem was that lp was loaded.  When I remove that, my call to
parport_register_device returns success! 

Thanks for your help!

Regards,
Kathy 



-----Original Message-----
From: Miguel Ojeda [mailto:miguel.ojeda.sandonis@gmail.com] 
Sent: Friday, April 25, 2008 2:18 PM
To: Alan Cox
Cc: Kathy Frazier; linux-kernel@vger.kernel.org
Subject: Re: Talking to parallel port in 2.6 kernel without using parport

>  > Can you tell me what I am missing?  Where can I get the actual 
> source code  > that goes with this version to further unravel this?

About two years ago (~2.6.18) I wrote one driver that needed exclusive
access to the parallel port and, like this time, Alan Cox guided me (thank
you Alan!). If you want, you can check the code at
drivers/auxdisplay/ks0108.c. I tested it as of 2.6.25 and worked fine, so it
could be a good reference for you. In addition, the code is pretty
straightforward!

>
>  To be honest this area of the kernel hasn't changed much over recent  
> times. Let me know if you can't figure out what is going on.
>

Right, I haven't had to change the code since 2.6.18.

--
Miguel Ojeda


  reply	other threads:[~2008-04-28 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 12:08 Talking to parallel port in 2.6 kernel without using parport Kathy Frazier
2008-04-14 12:39 ` Alan Cox
2008-04-22 18:34   ` Kathy Frazier
2008-04-25 17:12     ` Alan Cox
2008-04-25 18:18       ` Miguel Ojeda
2008-04-28 18:06         ` Kathy Frazier [this message]
2008-04-28 19:35           ` Miguel Ojeda
2008-04-28 17:59       ` Kathy Frazier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004301c8a95a$906666c0$b1333440$@com' \
    --to=kfrazier@daetwyler-rd.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox