linux-kernel - Re: [PATCH -v2 00/16] PCI: Re-factor PCI's 'latency timer' setup

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:	Mon, 31 Oct 2011 10:08:18 -0600
From:	Myron Stowe <myron.stowe@...il.com>
To:	Mike Frysinger <vapier@...too.org>
Cc:	Myron Stowe <myron.stowe@...hat.com>, jbarnes@...tuousgeek.org,
	linux-pci@...r.kernel.org, linux@....linux.org.uk,
	dhowells@...hat.com, ysato@...rs.sourceforge.jp,
	tony.luck@...el.com, fenghua.yu@...el.com, monstr@...str.eu,
	ralf@...ux-mips.org, benh@...nel.crashing.org, paulus@...ba.org,
	lethal@...ux-sh.org, davem@...emloft.net, cmetcalf@...era.com,
	gxt@...c.pku.edu.cn, tglx@...utronix.de, mingo@...hat.com,
	chris@...kel.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -v2 00/16] PCI: Re-factor PCI's 'latency timer' setup

On Fri, Oct 28, 2011 at 6:46 PM, Mike Frysinger <vapier@...too.org> wrote:
> On Fri, Oct 28, 2011 at 23:47, Myron Stowe wrote:
>>  - * blackfin and h8300 architectures do not seem to support PCI (no
>>   root bus scanning etc. exists within them) but they do have PCI header
>>   files.
>
> correct, all Blackfin parts in current mainline lack any sort of PCI
> support.  the header existence (iirc) is two fold:
>  - a lot of drivers like to use the pci/dma interface to manage memory
> instead of a pure dma interface
>  - BF535 has pci support, but we don't support that, and have largely
> dropped anything related to it
>
> so if this compile passes for Blackfin, it should be fine.  however,
> i'm lazy, so i don't suppose you've got a branch somewhere for me to
> pull to quickly compile test ?  if not, simply putting it into a
> branch that gets into linux-next should be sufficient as i think
> Stephen had Blackfin coverage in there ...

Hi Mike,

Don't blame you for being lazy, maintainership is not a fun task.  I do not
have a cross compile environment so could not compile test Blackfin so
I really would be interested in such.  I don't want to rely on linux-next if at
all possible as I already tried that once - unsuccessfully.

The three architectures I would really like to get compile tested and feedback
from the maintainers are: ARM, Blackfin, and H3/800.  To compile test
Blackfin would only require pulling in patches 01/16 and 10/16 (which would
be the same for H3/800) so if that wouldn't be too much of a pain I would really
appreciate it.  I do not have a branch from which you could pull but I
am willing
to look into such and give it a try.

Myron


> -mike
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
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/