linux-kernel - RE: [PATCH 4/6] Add multi mport support.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ABF87B0B6A38C0458E319AC973ED68AEC3DEFF@zch01exm26.fsl.freescale.net>
Date:	Mon, 18 Feb 2008 15:33:31 +0800
From:	"Zhang Wei" <Wei.Zhang@...escale.com>
To:	"Matt Porter" <mporter@...nel.crashing.org>
Cc:	"Kumar Gala" <galak@...nel.crashing.org>,
	<linuxppc-dev@...abs.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 4/6] Add multi mport support.

Hi, Matt,

So glad to see you again!

> -----Original Message-----
> From: Matt Porter [mailto:mporter@...nel.crashing.org] 
> On Thu, Jan 31, 2008 at 02:30:13PM +0800, Zhang Wei wrote:
> > > -----Original Message-----
> > > From: Kumar Gala [mailto:galak@...nel.crashing.org] 
> > > when we have multiple ports are the device IDs on the 
> ports intended  
> > > to be unique only to a port or unique across all ports?
> > > 
> > I consider each RIO controller will has its own network, 
> the device IDs
> > should be
> > unique only in its port network.
> 
> This is a bad assumption IMHO. It pushes policy on to the system
> designer of a RapidIO network.

I know it is a real bad assumption. However, the RIO initial ID is only
transported to
 driver by kernel parameter "riohdid", which can not distinguish the
multi
 rio controllers. It may be more better add a "rio-id" property in RIO
dts node, but
 the u-boot need some changes to support the rio-id assignment.

Cheers!
Wei.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/