Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030722AbWKUGsp (ORCPT ); Tue, 21 Nov 2006 01:48:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030681AbWKUGsp (ORCPT ); Tue, 21 Nov 2006 01:48:45 -0500 Received: from gate.crashing.org ([63.228.1.57]:31390 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S1030723AbWKUGso (ORCPT ); Tue, 21 Nov 2006 01:48:44 -0500 Subject: Re: bus_id collisions From: Benjamin Herrenschmidt To: Greg KH Cc: Linux Kernel list In-Reply-To: <20061121064122.GA10510@kroah.com> References: <1164081736.8207.14.camel@localhost.localdomain> <20061121064122.GA10510@kroah.com> Content-Type: text/plain Date: Tue, 21 Nov 2006 17:49:20 +1100 Message-Id: <1164091760.5597.18.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 684 Lines: 20 > Oh, that's a very annoying bus id, but I guess it's legal. > > I'll poke around and see if I can make it bigger. You don't want it > bigger for static 'struct device' types, right? Don't bother too much if it's complicated. I'm trying other options as well, like possibly using the Open Firmware "phandle" (sort of object ID) which is only 32 bits, provided I can get the embedded folks to agree to have one at all... Cheers, Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/