linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Johann Wilhelm <johann.wilhelm@student.tugraz.at>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-usb@vger.kernel.org, preining@logic.at,
	kristoffer.ericson@gmail.com, drussell@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: Add the infamous Huawei E220 to option.c
Date: Thu, 29 Nov 2007 08:44:38 +0100	[thread overview]
Message-ID: <200711290844.39428.oliver@neukum.org> (raw)
In-Reply-To: <20071129073303.1913505tnv2m8v0g@webmail.tugraz.at>

Am Donnerstag, 29. November 2007 07:33:03 schrieb Johann Wilhelm:
> But in my opinion the the modul-load-order should be forced by udev...  
> this should work and we only have 1 position to keep in mind if we eg.  
> get a new E220, support for the E270 or something else...

No, udev cannot help here because any of the two modules may already
be loaded when you plug in your device. You also need to get the kernel space
probing corrected. Basically you have three options.

1. Make both drivers handle the issue. That means code duplication
2. Make the option driver fail gracefully in probe()
3. Make sure usbcore doesn't probe the devices in the wrong mode with the 
option driver

	Regards
		Oliver


  reply	other threads:[~2007-11-29  7:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  0:13 Add the infamous Huawei E220 to option.c Pete Zaitcev
2007-11-29  6:33 ` Johann Wilhelm
2007-11-29  7:44   ` Oliver Neukum [this message]
2007-11-29  8:01     ` Pete Zaitcev
2007-11-29  8:14       ` Oliver Neukum
2007-11-29  9:09         ` Matthew Dharm
2007-11-29 10:01           ` Rui Santos
2007-11-29 10:49             ` Oliver Neukum
2007-11-29 11:07               ` Rui Santos
2007-11-29 11:55                 ` Oliver Neukum
2007-11-29 14:05                   ` Johann Wilhelm
2007-11-29 14:36                     ` Kristoffer Ericson
2007-11-29 14:41                       ` Oliver Neukum
2007-11-29 18:53                     ` Jaime Velasco Juan
2007-11-29 23:23                       ` Oliver Neukum
2007-11-30 16:30                         ` [PATCH] USB: option: Bind to the correct interface of the Huawei E220 Jaime Velasco Juan
2007-12-01  8:07                           ` Norbert Preining
2007-12-01  8:34                             ` Pete Zaitcev
2007-12-01 10:04                               ` Norbert Preining
2007-12-01 18:36                           ` Borislav Petkov
2007-12-05 16:34                           ` Pete Zaitcev
2007-12-05 18:23                             ` Oliver Neukum
2007-12-05 19:14                               ` Pete Zaitcev
2007-11-29 19:12                   ` Add the infamous Huawei E220 to option.c Rui Santos
2007-11-29 17:08       ` Greg KH
2007-11-29  7:38 ` Oliver Neukum
2007-11-29  7:52   ` Pete Zaitcev
2007-11-29  8:04     ` Oliver Neukum
2007-11-29  8:10       ` Pete Zaitcev
2007-11-29 14:14 ` Norbert Preining
2007-11-29 14:16   ` Norbert Preining

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=200711290844.39428.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=drussell@redhat.com \
    --cc=johann.wilhelm@student.tugraz.at \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=zaitcev@redhat.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;
as well as URLs for NNTP newsgroup(s).