LKML Archive on
help / color / mirror / Atom feed
From: David Brownell <>
To: Randy Dunlap <>
Cc: Linux Kernel list <>,
	Jean Delvare <>, Greg KH <>
Subject: Re: [patch/rfc 2.6.20-git] parport reports physical devices
Date: Sun, 18 Feb 2007 21:52:53 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sunday 18 February 2007 9:28 pm, Randy Dunlap wrote:
> On Sun, 18 Feb 2007 21:08:07 -0800 David Brownell wrote:
> > Currently a parport_driver can't get a handle on the device node for the
> > underlying parport (PNPACPI, PCI, etc).  That prevents correct placement
> > of sysfs child nodes, which can affect things like power management.
> > 
> > This patch resolves that issue for non-legacy configurations:
> > ...
> Does this patch address ?

I don't think it would affect that behavior, but surprises can happen;
like the root cause of 5496 being the lack of hookup to the real device.

> What are you wondering about parport DMA?

First, whether it ever worked on ports enumerated through PNP.

After all, I saw it oops there, ergo the surprisingly-far-afield
parts of this patch to update PNP so it now sets up DMA masks.
(Which, I was thinking, probably matters mostly for parport;
but I'm just assuming 24-bit masks are correct there.)

> Please see
> and

Suggesting that no, it's never worked on ports enumerated
through PNP.  There's a possibility that if it previously
worked through PCI, it now works ... someone with a parport
printer could check it out.

- Dave

  reply	other threads:[~2007-02-19  5:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  5:08 David Brownell
2007-02-19  5:28 ` Randy Dunlap
2007-02-19  5:52   ` David Brownell [this message]
2007-02-19 14:18 ` Jean Delvare
2007-02-19 16:40   ` David Brownell
2007-02-20 21:10     ` Jean Delvare
2007-02-24 21:40       ` David Brownell
2007-02-24 21:49       ` David Brownell

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:

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

  git send-email \ \ \ \ \ \ \
    --subject='Re: [patch/rfc 2.6.20-git] parport reports physical devices' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).