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]

Date:	Thu, 24 May 2007 00:59:44 +0400
From:	Manu Abraham <abraham.manu@...il.com>
To:	Greg KH <greg@...ah.com>
CC:	linux-pci@...ey.karlin.mff.cuni.cz,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCIE

Greg KH wrote:
> On Wed, May 23, 2007 at 04:15:01PM +0400, Manu Abraham wrote:
>> Hi,
>>
>> Do the PCI Express chipsets also use the same PCI API ?
> 
> At the Linux kernel driver level, yes, they do.
> 
>> The device
>> specifications are thus for the device that i am looking at:
>>
>>  PCI Express interface
>>
>>     * Compliant to PCI Express Base Specification 1.0a
>>     * The PCI Express circuit supports isochronous data traffic intended
>> for uninterrupted transfer of streaming data like video streaming
>>           o x1 PCI Express endpoint (2.5 Gbit/s)
>>           o Data and clock recovery from serial stream
>>           o Low jitter and BER
>>     * Type 0 configuration space header
>>           o 64-bit addressing
>>           o Single BAR; programmable address range of 17 bits, 18 bits,
>> 19 bits or 20 bits dependent on application requirements
>>     * PCI Express capabilities
>>           o 128 bytes write packet size and 64 bytes read packet size
>>           o MSI support
>>           o Software directed power management of four device power
>> states (D0 to D3)
>>           o Active state power management of link states
>>           o Vendor specific capability for VC1 support; after reset VC1
>> isochronous capability is disabled
>>
>> I have been trying the said card with a normal PCI style driver, but
>> while booting the kernel (2.6.21.1) i do get a message like this (an
>> Intel DP965LT motherboard with BIOS version:
>> MQ96510J.86A.1612.2006.1227.1513)
>> Also accessing the interrupt registers causes a hard freeze, for which
>> only the RESET button seems to be of any help.
>>
>> Uncompressing Linux .. Ok, booting the kernel.
>> BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw
>> vendor)
>> PCI: Failed to allocate mem resource #6:20000@...00000 for 0000:01:00.0
>>
>> Any ideas as to what could be wrong ?
> 
> What type of PCI device is this?  What driver is controlling it?  What
> is the output of 'lspci -v' at boot time?

Err .. how do i get lspci -v at boot time ? You mean without any driver
loaded , i presume.

The device is a new DTV bridge from NXP (SAA7162E) with a PCIe interface.

06:00.0 Multimedia controller: Philips Semiconductors Unknown device
7162 (rev 01)
        Subsystem: Twinhan Technology Co. Ltd Unknown device 0027

Currently working on a driver for the same. I am attaching lspci -v as
well as lspci -vvn outputs.


Thanks,
Manu

View attachment "lspci-v.txt" of type "text/plain" (11912 bytes)

View attachment "lspci-vvn.txt" of type "text/plain" (56835 bytes)