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: <8bd0f97a0805201621j449ad2a5s7c24e1a48c3aa31c@mail.gmail.com>
Date:	Tue, 20 May 2008 19:21:03 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Russell King" <rmk+lkml@....linux.org.uk>
Cc:	"Javier Herrero" <jherrero@...istemas.es>,
	"Linux Kernel List" <linux-kernel@...r.kernel.org>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Bryan Wu" <cooloney@...nel.org>
Subject: Re: b4aa54d951d38d7a989d6b6385494ef5ea7371d7 breaks some serial configurations

On Tue, May 20, 2008 at 7:13 PM, Russell King wrote:
> On Tue, May 20, 2008 at 12:52:52PM +0200, Javier Herrero wrote:
>> I see... would be OK to move the asm/serial.h include to its original
>> position and to modify the asm-blackfin/serial.h in this way to avoid
>> duplicate definition warnings, or would it be too ugly?:
>
> Can blackfin systems accept PCMCIA cards?  Or PCI cards?  In which case
> you probably don't want to implement this support like this.

yes, you can hook PCMCIA cards up to a Blackfin proc (and we have).
we probably wont be supporting PCI since it tends to require MMU
support, and at least with all the Blackfins we support now, none have
PCI support on-chip.
-mike
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ