linux-kernel - Re: PCIE

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: <465A2F6F.6070900@gmail.com>
Date:	Mon, 28 May 2007 05:25:03 +0400
From:	Manu Abraham <abraham.manu@...il.com>
To:	Roland Dreier <rdreier@...co.com>
CC:	Grant Grundler <grundler@...isc-linux.org>,
	Greg KH <greg@...ah.com>, linux-pci@...ey.karlin.mff.cuni.cz,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCIE

Roland Dreier wrote:
>  > >> Another question would be if the device supports multiple messages, MSIX
>  > >> should be used ?
>  > > 
>  > > Yes. Assuming the device supports multiple MSI-X messages.
> 
> At least on my device (PCI ID 1131:7162) there is no MSI-X capability,
> so that's not an option for you.  The current Linux implementation
> does not support more than one MSI interrupt, so you just get one
> interrupt with pci_enable_msi().
> 
> I think it's probably simplest for you to forget about MSI until you
> have the basic driver working.

Damn. The NXP guys don't want me to go ahead with the generic registers.

What they said :

> And if you really use the SAA7162 in the PC application,
> pls ignore the 0x520 .....
> That's not a good decision to use that.

Might need to ask them why it would not be a good decision then. :-(
-
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/