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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ABF87B0B6A38C0458E319AC973ED68AEBD0677@zch01exm26.fsl.freescale.net>
Date:	Thu, 31 Jan 2008 13:57:25 +0800
From:	"Zhang Wei" <Wei.Zhang@...escale.com>
To:	"Kumar Gala" <galak@...nel.crashing.org>
Cc:	<mporter@...nel.crashing.org>, <linux-kernel@...r.kernel.org>,
	<linuxppc-dev@...abs.org>
Subject: RE: [PATCH 4/6] Add multi mport support.

> -----Original Message-----
> From: Kumar Gala [mailto:galak@...nel.crashing.org] 
> 
> On Jan 30, 2008, at 4:30 AM, Zhang Wei wrote:
> 
> > Change lots of static variable to mport private. And add 
> mport to some
> > function declaration.
> 
> Can you explain this patch further.  Its not clear exactly from this  
> commit message why we are doing this.
> 
> - k

Sorry about I have a little hurry about it.

The original RapidIO driver suppose there is only one mpc85xx RIO
controller
in system. So, some data structures are defined as mpc85xx_rio global,
such as 'regs_win', 'dbell_ring', 'msg_tx_ring'. Now, I changed them to
mport's private members. And you can define multi RIO OF-nodes in dts
file
for multi RapidIO controller in one processor, such as PCI/PCI-Ex host
controllers
in Freescale's silicon. And the mport operation function declaration
should be changed
to know which RapidIO controller is target.

Thanks!
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/