From: Josh Litherland <fauxpas@sade.emperorlinux.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux and IBM : "unauthorized" mini-PCI : TCPA updates
Date: Tue, 3 Jun 2003 14:29:37 -0400 (EDT) [thread overview]
Message-ID: <20030603182937.BBFF86207B@sade.emperorlinux.com> (raw)
In-Reply-To: <1054658054.9359.49.camel@dhcp22.swansea.linux.org.uk>
In article <1054658054.9359.49.camel@dhcp22.swansea.linux.org.uk> you wrote:
> Secondly TCPA doesn't require such a restriction. A TCPA system can have
> hardware whitelists so that the TCPA chip refuses to do any TCPA with
> unknown devices present (since they may be hostile) but it doesn't have
> to fail to boot in this case.
Interestingly, when the offending device is a modem, it will warn in
the BIOS but will neither disable the device nor refuse to boot. Only
when a wireless NIC is inserted will it grind to a bloody halt.
--
Josh Litherland (josh@emperorlinux.com)
next prev parent reply other threads:[~2003-06-03 18:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 16:49 Linux and IBM : "unauthorized" mini-PCI : TCPA updates Lincoln Durey
2003-06-03 16:34 ` Alan Cox
2003-06-03 18:29 ` Josh Litherland [this message]
2003-06-03 17:04 ` Michael Frank
2003-06-03 17:42 ` Timothy Miller
2003-06-04 12:39 ` Derek Fawcus
2003-06-06 22:59 ` Martin List-Petersen
2003-06-09 12:57 ` Dana Lacoste
2003-06-09 16:56 ` Martin List-Petersen
2003-06-10 23:35 ` Theodore Ts'o
2003-07-07 18:12 ` Linux and IBM : "unauthorized" mini-PCI : Cisco mpi350 _way_ sub-optimal Lincoln D. Durey
2003-07-08 14:02 ` Alan Cox
2003-07-08 15:20 ` Gerald Britton
2003-07-08 15:42 ` Alan Cox
2003-07-08 17:24 ` Gerald Britton
2003-07-08 17:44 ` Russell King
2003-07-08 20:58 ` Jamie Lokier
2003-07-09 22:35 ` Gerald Britton
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 19:35 Linux and IBM : "unauthorized" mini-PCI : TCPA updates Mark Grosberg
2003-06-03 19:40 ` Mike Dresser
2003-06-03 20:02 ` Josh Litherland
2003-06-03 20:40 ` Mike Dresser
2003-06-03 21:09 ` Josh Litherland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030603182937.BBFF86207B@sade.emperorlinux.com \
--to=fauxpas@sade.emperorlinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.