From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263185AbTDVOwj (ORCPT ); Tue, 22 Apr 2003 10:52:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263184AbTDVOwj (ORCPT ); Tue, 22 Apr 2003 10:52:39 -0400 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:3806 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S263185AbTDVOwh (ORCPT ); Tue, 22 Apr 2003 10:52:37 -0400 Subject: Re: mangled isapnp IDs in /proc/bus/isapnp/devices From: Alan Cox To: Rene Rebe Cc: Linux Kernel Mailing List In-Reply-To: <20030422.114614.846960661.rene.rebe@gmx.net> References: <20030422.114614.846960661.rene.rebe@gmx.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1051020403.14880.7.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Apr 2003 15:06:43 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Maw, 2003-04-22 at 10:46, Rene Rebe wrote: > Hi all, > > is there a reason why the isapnp device id are mangled this way: This is how the spec says the names work