From: Justin Schoeman <justin@expertron.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Re: can't seem to ignore a battery
Date: Fri, 13 Nov 2009 14:43:35 +0000 [thread overview]
Message-ID: <4AFD7097.3080500@expertron.co.za> (raw)
In-Reply-To: <29507.1258042014@foxharp.boston.ma.us>
I am not subscribed to linux-hotplug, but am following this thread on
the list archive.
This is exactly the problem I am having with my Huawei E220 modem. (The
modem has a usb cdrom device with the Windows drivers.) The cdrom
emulation on the device is broken, so userland attempts to mount the
device trigger a device reset.
The network operators don't care, because the device works under
Windows, and that is all they support. So getting the firmware fixed is
not an option.
The Linux kernel guys do not want to put work arounds for buggy hardware
(just about every Huawei device type has broken the cdrom/scsi protocol
in some obscure, but different way) into generic code. They recommend
that seeing as the bug is triggered from userspace, it must be fixed in
userspace.
With HAL, it was a simple one-line fix, and the device was ignored by
all applications, and everything worked perfectly. Doing the same in
udev is proving very tricky.
If you can please advise on how to block this in udev, or the correct
place to add the fix in the userland apps/scripts, I would appreciate it.
Thanks,
Justin
next prev parent reply other threads:[~2009-11-13 14:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 16:06 can't seem to ignore a battery Paul Fox
2009-11-12 16:50 ` David Zeuthen
2009-11-12 17:33 ` Richard Hughes
2009-11-12 17:40 ` Paul Fox
2009-11-12 17:43 ` David Zeuthen
2009-11-13 2:01 ` Kay Sievers
2009-11-13 2:44 ` Paul Fox
2009-11-13 4:54 ` Greg KH
2009-11-13 14:13 ` Kay Sievers
2009-11-13 14:33 ` Paul Fox
2009-11-13 14:43 ` Justin Schoeman [this message]
2009-11-13 16:48 ` Greg KH
2009-11-13 16:49 ` Greg KH
2009-11-13 17:29 ` Justin Schoeman
2009-11-13 17:38 ` Greg KH
2009-11-13 18:22 ` Justin Schoeman
2009-11-13 18:43 ` Paul Fox
2009-11-13 20:33 ` Greg KH
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=4AFD7097.3080500@expertron.co.za \
--to=justin@expertron.co.za \
--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).