From: George Anzinger <george@mvista.com>
To: Greg KH <greg@kroah.com>
Cc: Matt Mackall <mpm@selenic.com>,
"Amit S. Kale" <amitkale@emsyssoft.com>,
Andrew Morton <akpm@osdl.org>,
jim.houston@comcast.net, discuss@x86-64.org, ak@suse.de,
shivaram.upadhyayula@wipro.com,
lkml <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [discuss] Re: kgdb for x86_64 2.6 kernels
Date: Wed, 14 Jan 2004 16:02:45 -0800 [thread overview]
Message-ID: <4005D8A5.3010002@mvista.com> (raw)
In-Reply-To: <20040114232631.GB9983@kroah.com>
Greg KH wrote:
> On Wed, Jan 14, 2004 at 12:02:02PM -0800, George Anzinger wrote:
>
>>Right. I had hoped that we might one day be able to use the USB and I am
>>sure there are others.
>
>
> Raw USB? Or some kind of USB to serial device?
>
> Remember, USB needs interrupts to work, see the kdb patches for the mess
> that people have tried to go through to send usb data without interrupts
> (doesn't really work...)
I gave up on USB when I asked the following questions:
1. How many different HW USB master devices need to be supported (i.e. appear on
your normal line of MBs)? (answer, too many)
2. Can I isolate a USB port from the kernel so that it does not even know it is
there? (answer: NO)
What I want is a USB port that is completely coded in kgdb software (keeps
Heisenberg out). It would be a polled device except for the ^C (or equivalent)
interrupt.
We, of course, have the same issues with the eth interface. Far too much of the
rest of the kernel is involved in the communications with it. Also there are
way to many interfaces to code each one seperatly, thus the current effort using
a good deal of the kernel to remove all that special code. Of course Heisenberg
and all his friends and relations are taking up residence in that code :) Might
not be too bad except that his uncle is Murphy.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-01-15 0:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000e01c3d476$2ebe03a0$4008720a@shivram.wipro.com>
[not found] ` <1073603622.993.353.camel@new.localdomain>
[not found] ` <20040108153243.11e45156.akpm@osdl.org>
[not found] ` <200401091031.41493.amitkale@emsyssoft.com>
2004-01-09 22:16 ` [discuss] Re: kgdb for x86_64 2.6 kernels George Anzinger
2004-01-10 10:41 ` Amit S. Kale
2004-01-10 15:03 ` Pavel Machek
2004-01-10 18:14 ` Pavel Machek
2004-01-12 14:32 ` Amit S. Kale
2004-01-10 19:30 ` Pavel Machek
2004-01-12 14:31 ` Amit S. Kale
2004-01-12 6:00 ` George Anzinger
2004-01-12 9:47 ` Pavel Machek
2004-01-13 20:55 ` George Anzinger
2004-01-12 14:50 ` Amit S. Kale
2004-01-13 21:26 ` George Anzinger
2004-01-14 6:31 ` Matt Mackall
2004-01-14 20:02 ` George Anzinger
2004-01-14 23:26 ` Greg KH
2004-01-15 0:02 ` George Anzinger [this message]
2004-01-15 0:19 ` Pavel Machek
2004-01-15 3:28 ` George Anzinger
2004-01-15 0:23 ` Greg KH
2004-01-15 3:30 ` George Anzinger
2004-01-14 13:24 ` Amit S. Kale
2004-01-14 22:32 ` George Anzinger
[not found] <1cd9t-4Su-65@gated-at.bofh.it>
[not found] ` <1coR2-42n-19@gated-at.bofh.it>
[not found] ` <1d3r0-1tw-3@gated-at.bofh.it>
[not found] ` <1dbI9-89t-7@gated-at.bofh.it>
[not found] ` <1dEqx-F0-1@gated-at.bofh.it>
[not found] ` <1dMRc-6DQ-3@gated-at.bofh.it>
[not found] ` <1e2Mk-6YA-17@gated-at.bofh.it>
[not found] ` <1e2Mo-6YA-31@gated-at.bofh.it>
[not found] ` <1e3fi-4nG-5@gated-at.bofh.it>
2004-01-15 8:02 ` Andi Kleen
2004-01-15 8:36 ` George Anzinger
2004-01-15 8:52 ` Andi Kleen
2004-01-16 1:15 ` Matt Mackall
2004-01-16 18:04 ` Randy.Dunlap
2004-01-16 21:07 ` Andi Kleen
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=4005D8A5.3010002@mvista.com \
--to=george@mvista.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=amitkale@emsyssoft.com \
--cc=discuss@x86-64.org \
--cc=greg@kroah.com \
--cc=jim.houston@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@ucw.cz \
--cc=shivaram.upadhyayula@wipro.com \
/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