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] [day] [month] [year] [list]

Message-ID: <ca2dc2820804281235n533f1daam26a5c064829165dc@mail.gmail.com>
Date:	Mon, 28 Apr 2008 21:35:00 +0200
From:	"Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>
To:	"Kathy Frazier" <kfrazier@...twyler-rd.com>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Talking to parallel port in 2.6 kernel without using parport

On Mon, Apr 28, 2008 at 8:06 PM, Kathy Frazier
<kfrazier@...twyler-rd.com> wrote:
> 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.

I'm glad the code is helpful.

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

Yeah, I made the same mistake two years ago too. ;)

>
>  Thanks for your help!
>

You are welcome!

--
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/