From: Greg KH <greg@kroah.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Ian Morgan <imorgan@webcon.ca>,
helpdeskie@bencastricum.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 Sensors & USB problems
Date: Tue, 4 May 2004 13:37:38 -0700 [thread overview]
Message-ID: <20040504203738.GJ24802@kroah.com> (raw)
In-Reply-To: <20040418075140.6c118202.khali@linux-fr.org>
On Sun, Apr 18, 2004 at 07:51:40AM +0200, Jean Delvare wrote:
> > Can anyone explain, however, why my i2c bus showed up as number 0
> > under linux <= 2.6.4, and now always as number 1 under linux 2.6.5?
> > The is no number 0 any more.
>
> The bus number allocation scheme is such that once a number has been
> used once (since the machine last booted) it will not be used again.
> This is admittedly not ideal and should be fixed. I suspect that the fix
> isn't trivial because the current structures would make the new scheme
> have a poor algorithmic complexity (O(2) maybe), but I haven't checked
> yet. Greg, can you confirm?
It's not due to the complexity, it's just due to the fact that I haven't
gotten around to doing it yet :)
Patches to fix this are gladly welcome if the current situation really
bothers people. No userspace tools should have a problem with the way
things are right now. If they do have problems, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-04 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 14:56 2.6.5 Sensors & USB problems Jean Delvare
2004-04-17 22:07 ` Ian Morgan
2004-04-17 23:49 ` Ian Morgan
2004-04-18 5:51 ` Jean Delvare
2004-05-04 20:37 ` Greg KH [this message]
2004-05-06 17:41 ` Jean Delvare
2004-04-18 5:32 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 16:18 Ben Castricum
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=20040504203738.GJ24802@kroah.com \
--to=greg@kroah.com \
--cc=helpdeskie@bencastricum.nl \
--cc=imorgan@webcon.ca \
--cc=khali@linux-fr.org \
--cc=linux-kernel@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