From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: UDEV : ASUS Laptop G73S MultiCard Reader
Date: Sun, 17 Jul 2011 18:53:00 +0000 [thread overview]
Message-ID: <20110717185300.GA29648@kroah.com> (raw)
In-Reply-To: <4E217D77.7030503@gatworks.com>
On Sun, Jul 17, 2011 at 11:50:31AM -0400, Postmaster wrote:
>
> >That is because this is a different device, and it says it is a
> >vendor-specific protocol, which will not work with the usb-storage
> >driver, sorry.
>
> I Disagree with most of what u suggest.
I'm sorry to hear that.
> Who knows what vendor specific means. And you really wont know until
> you try. Which is why there are tables to handle Unusual Devices.
If a vendor says it is not a mass-storage device, why do you think they
are lying? And the term, "vendor specific" has a very specific
definition, see the USB specification if you are curious as to what it
is.
> At this time there is a realtek driver in the latest kern code. I
> would like to load up this driver when usb-core detects this device.
>
> Right now, I have not found the udev rule for loading up usb-storage.
There is no such rule, the usb device id causes it to happen through
modprobe of the module alias of the device.
> So where are the udev system specs
This is not something that udev does at all, sorry.
> BTW: is there a way to disable, and enable the device? Since this
> usb device is internal, if I have too many "printk" or DBG messages
> at boot-up time, it tends to overflow the rsyslogd daemon.
>
> btw#2 where is this forum? All one sees in the written docs is to
> email questions, rather than post questions to a forum.
Yes, this is done through email, not a web forum.
greg k-h
prev parent reply other threads:[~2011-07-17 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 12:00 UDEV : ASUS Laptop G73S MultiCard Reader Postmaster
2011-07-17 9:17 ` Greg KH
2011-07-17 15:50 ` Postmaster
2011-07-17 18:53 ` Greg KH [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=20110717185300.GA29648@kroah.com \
--to=greg@kroah.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).