From: ebiederm@xmission.com (Eric W. Biederman)
To: Stefan Reinauer <stepan@coresystems.de>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Peter Stuge <stuge-linuxbios@cdy.org>,
linux-kernel@vger.kernel.org, linuxbios@linuxbios.org
Subject: Re: [LinuxBIOS] #57: libusb host program for PLX NET20DC debug device
Date: Sun, 03 Dec 2006 06:11:57 -0700 [thread overview]
Message-ID: <m1ac25f7j6.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061203125250.GA17019@coresystems.de> (Stefan Reinauer's message of "Sun, 3 Dec 2006 13:52:50 +0100")
Stefan Reinauer <stepan@coresystems.de> writes:
> * Segher Boessenkool <segher@kernel.crashing.org> [061203 13:42]:
>> On LPC, yes -- or 0.5us or something like that. On ISA it's
>> a lot faster, on PCI too -- better do 20 or so outb's to be
>> safe.
>
> The value's actually something we have been using as a rule of thumb
> while doing outb to port 80. Don't think these are routed to LPC, are
> they?
Depends on the destination address. For 0x80 you can be fairly
certain it will be an unacknowledged cycle subtractively decoded
to the slowest bus on the system. Or routed to 32 PCI or the LPC bus
if there is something to actually looking at the value so it is slow.
Since all I need is something that delays for about 50ms 50,000 outb
to port 0x80 looks like a good first approximation, and since it
only happens once it is probably better to just bump that count up
instead of trying to be precise about it and have an accurate timer.
I'm not at all convinced a usb console can be made sufficiently solid
to be useful. But it is at least worth trying so we can clearly say
it doesn't work well.
Eric
next prev parent reply other threads:[~2006-12-03 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 2:43 Lu, Yinghai
2006-12-02 14:02 ` Eric W. Biederman
2006-12-02 20:47 ` yhlu
2006-12-03 11:51 ` Eric W. Biederman
2006-12-03 12:01 ` Stefan Reinauer
2006-12-03 12:42 ` Segher Boessenkool
2006-12-03 12:52 ` Stefan Reinauer
2006-12-03 13:11 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-01 22:10 Lu, Yinghai
2006-12-01 18:55 Lu, Yinghai
2006-12-01 19:19 ` Greg KH
2006-12-01 20:42 ` Peter Stuge
2006-12-01 21:15 ` Eric W. Biederman
2006-12-01 21:46 ` Peter Stuge
2006-12-01 23:02 ` Eric W. Biederman
2006-12-03 17:00 ` Peter Stuge
2006-12-03 23:03 ` Eric W. Biederman
2006-12-01 23:13 ` Eric W. Biederman
2006-12-03 15:49 ` Eric W. Biederman
2006-12-01 18:26 Lu, Yinghai
2006-12-01 18:41 ` Greg KH
2006-12-01 19:04 ` Peter Stuge
2006-12-01 19:17 ` Greg KH
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=m1ac25f7j6.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxbios@linuxbios.org \
--cc=segher@kernel.crashing.org \
--cc=stepan@coresystems.de \
--cc=stuge-linuxbios@cdy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome