From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [HACK] Give hiddev a device link in sysfs
Date: Tue, 23 Dec 2003 01:47:02 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107214418121487@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107153465903030@msgid-missing>
Greg KH wrote:
> On Mon, Dec 15, 2003 at 07:32:35PM -0500, Adam Kropelin wrote:
>> (/sys/class/usb/hiddevN/device). Further investigation showed that
>> the broken link is due to hiddev's being not-quite-a-usb-device and
>> having a zero kobj with no parent, etc.
>>
>> I cooked up the hack-job patch below and it seems to be working.
>> Clearly this isn't the right solution, but it's a starting point and
>> it solves my immediate need.
>
> Yeah, hiddev is wierd. It needs to dynamically allocate that
> interface structure, and then a patch like this will start to make
> sense. Right now bad things can happen if you unload the hiddev
> module when you have a file in sysfs open for that device.
>
> But this patch is a start. Care to finish it up?
Sure...I'll have a chance to look at it after the holidays.
--Adam
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2003-12-23 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 0:32 [HACK] Give hiddev a device link in sysfs Adam Kropelin
2003-12-22 20:42 ` Greg KH
2003-12-23 1:47 ` Adam Kropelin [this message]
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=marc-linux-hotplug-107214418121487@msgid-missing \
--to=akropel1@rochester.rr.com \
--cc=linux-hotplug@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).