From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Adam Belay <ambx1@neo.rr.com>,
linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk,
akpm@osdl.org, rml@ximian.com, greg@kroah.com
Subject: Re: [RFC][PATCH] driver model and sysfs support for PCMCIA (1/3)
Date: Mon, 19 Jul 2004 10:02:37 +0200 [thread overview]
Message-ID: <20040719080237.GB9494@dominikbrodowski.de> (raw)
In-Reply-To: <20040705224704.GA4090@neo.rr.com>
Hi Adam,
On Mon, Jul 05, 2004 at 10:47:04PM +0000, Adam Belay wrote:
> > - I like many ideas in your patches -- large parts of them, though, are
> > "double work" as similar things have already been submitted (by me)
> > to Russell on the linux-pcmcia mailing list. What's missing in my current
> > patches [proof-of-concepts do exist and had been announced both on lkml
> > and on said linux-pcmcia list, though] is the exporting of product and
> > manufactor ID and "vers_1" strings, because that needs better resource
> > handling.
> > - the resource_ready handling is "racy", at least. Resources can disappear
> > again.
>
> Could you provide an example of how resources will disappear again?
/etc/pcmcia/config.opts may include
include memory 0xc0000-0xfffff
exclude memory 0xc0000-0xfffff
even though it wouldn't make sense.
> My patch
> was designed so that even if they weren't available, nothing bad would happen.
> Furthermore, it rescans for devices when userspace attempts to bind a driver.
> Resources would almost certainly be available during that time,
Indeed, they _are_ available during that time, else userspace wouldn't know
what driver to bind. That's why my approach registers the pcmcia "sysfs"
device struct at that place.
> In other
> words, it seems that resource handling is a problem for all of pcmcia.
It is, but partly because used ioports and iomem are not 100% accounted in
/proc/ioports and /proc/iomem. I'm eagerly awaiting the creation of a PNP-
and/or ACPI-based resource core "backend", like you proposed at Kernel
Summit last year, IIRC, which possibly allows the PCMCIA core on x86{,_64}
to "trust" the resources not in the resource database to be available for
PCMCIA's use.
> It was to add minimal support for a much needed feature while introducing
> as few potential bugs as possible to a stable kernel series. I see 2.7 as
> the time for rewrites. With that in mind, I consider your patches to be a
> great solution, but I'm worried about changing internal ds functionality
> during 2.6.
However, adding pcmcia devices at the place you suggest causes resource
headaches and makes merging my patches in 2.7. much more difficult. So,
could we work to a compromise patch where PCMCIA sysfs device structs are
only registered at "bind" time [as long as Russell agrees, that is...]?
Also, what do we need the "hotplug" export for? I'd like to avoid backwards
compatibility trouble in future, and as users _need_ to run cardmgr hotplug
seems to be without usage now.
Dominik
next prev parent reply other threads:[~2004-07-19 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 20:02 Adam Belay
2004-06-29 5:57 ` Dmitry Torokhov
2004-06-29 8:46 ` Russell King
2004-06-29 19:09 ` Dominik Brodowski
2004-07-05 22:47 ` Adam Belay
2004-07-19 8:02 ` Dominik Brodowski [this message]
2004-07-26 13:53 ` Adam Belay
2004-07-27 18:27 ` Dominik Brodowski
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=20040719080237.GB9494@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=akpm@osdl.org \
--cc=ambx1@neo.rr.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=rml@ximian.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
all inboxes | Powered by JetHome®