From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Kathy Frazier" <kfrazier@daetwyler-rd.com>
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: Fri, 25 Apr 2008 18:12:19 +0100 [thread overview]
Message-ID: <20080425181219.61e29b1f@core> (raw)
In-Reply-To: <006f01c8a4a7$82e37ea0$88aa7be0$@com>
> One of our engineers downloaded source code a while back from
> linux-2.6.18-rc7, but I am not sure how close that is to what is installed
> on my system (uname -r returns 2.6.18-1.2798.fc6. When I set my printk to 8
> (echo 8 > /proc/sys/kernel/printk), there are no messages shown on the
> failure. According to the source code I have, the only silent failure in
> parport_register_device is:
Nothing immediately strikes me.
> When I change the flags from PARPORT_FLAG_EXCL to 0 in the call to
> parport_register_device, the call returns a non-zero to indicate success.
Do you have the printer driver loaded already ? (and does it behave if
you do rmmod lp first)
> 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?
>From the .fc6 it would be an old Fedora kernel so very close to standard
2.6.18 from kernel.org, but the Fedora Core kernels are available from
the Fedora download pages - the .srpm package for each kernel is the one
matching the same binary - so google for "2.6.18-1.2798.fc6.src.rpm"
http://www.mjmwired.net/resources/mjm-fedora-fc6.html has a few notes on
it.
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.
next prev parent reply other threads:[~2008-04-25 17:19 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 [this message]
2008-04-25 18:18 ` Miguel Ojeda
2008-04-28 18:06 ` Kathy Frazier
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=20080425181219.61e29b1f@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kfrazier@daetwyler-rd.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).