linux-kernel - RE: Talking to parallel port in 2.6 kernel without using parport

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 14:06:20 -0400
From:	"Kathy Frazier" <kfrazier@...twyler-rd.com>
To:	"'Miguel Ojeda'" <miguel.ojeda.sandonis@...il.com>,
	"'Alan Cox'" <alan@...rguk.ukuu.org.uk>
Cc:	"'Kathy Frazier'" <kfrazier@...twyler-rd.com>,
	<linux-kernel@...r.kernel.org>
Subject: RE: Talking to parallel port in 2.6 kernel without using parport

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@...il.com] 
Sent: Friday, April 25, 2008 2:18 PM
To: Alan Cox
Cc: Kathy Frazier; linux-kernel@...r.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/