From mboxrd@z Thu Jan  1 00:00:00 1970
From: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: Re: Populating netdev::dev_id for udev discrimination
Date: Mon, 10 Mar 2014 13:18:23 +0100
Message-ID: <531DAD8F.7090602@hartkopp.net>
References: <1394294420.3356.15.camel@NREC-014563> <531CBB6F.7090803@pengutronix.de> <531D6D3B.9020900@hartkopp.net> <20140310104650.GA456@vandijck-laurijssen.be> <531D9B6F.9010603@pengutronix.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <linux-can-owner@vger.kernel.org>
Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.219]:11735 "EHLO
	mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752694AbaCJMS1 (ORCPT
	<rfc822;linux-can@vger.kernel.org>); Mon, 10 Mar 2014 08:18:27 -0400
In-Reply-To: <531D9B6F.9010603@pengutronix.de>
Sender: linux-can-owner@vger.kernel.org
List-ID: <linux-can.vger.kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>, "Christopher R. Baker" <cbaker@rec.ri.cmu.edu>
Cc: linux-can@vger.kernel.org

On 10.03.2014 12:01, Marc Kleine-Budde wrote:

> 
> You can create a patch against the testing branch of linux-can-next[1]
> 

FYI:

Tested with PEAK PCAN USB pro and EMS PCMCIA (both with two channels) and the
dev_id works like expected (first channel dev_id = 0x0, second channel 0x1).

Tnx
Oliver