From: Jack F Vogel <jfv@bluesong.net>
To: Keith Owens <kaos@sgi.com>
Cc: Saravanan s <saravanan.mainker@gmail.com>,
kdb@oss.sgi.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Announce: kdb v4.4 is available for kernel 2.6.10
Date: Mon, 24 Jan 2005 21:52:18 -0800 [thread overview]
Message-ID: <20050125055218.GA15014@trane.bluesong.net> (raw)
In-Reply-To: <15313.1106628266@kao2.melbourne.sgi.com>
On Tue, Jan 25, 2005 at 03:44:26PM +1100, Keith Owens wrote:
> On Tue, 25 Jan 2005 09:55:55 +0530,
> Saravanan s <saravanan.mainker@gmail.com> wrote:
> >Hi Keith,
> >
> >> I have no hardware to test on, so I have
> >> to rely on HP to keep the USB patches in KDB up to date.
> >
> >Does that mean that there is USB support for KDBv4.4 for kernel 2.6
> >for i386 machines? Or the patch for i386 also comes from the HP guys.
>
> All the USB console patches for kdb came from HP, both i386 and ia64.
> Neither work in 2.6 kernels at the moment.
I have been looking at the USB code and talked with gregkh about
it a bit, it looks to me that in order for this to work its going
to take a self-contained polling driver. I've been busy so I havent
looked too far yet for any pre-existent code that could be utilized.
It may need to be written from scratch, which I also might attempt
once I get my queue a bit reduced.
But as is the code thats there isnt even close to working, its just
a bit of infrastructure.
Cheers,
Jack
next prev parent reply other threads:[~2005-01-25 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 15:21 gowda_avinash
2005-01-24 15:34 ` Keith Owens
2005-01-25 4:25 ` Saravanan s
2005-01-25 4:44 ` Keith Owens
2005-01-25 5:52 ` Jack F Vogel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-25 12:17 Keith Owens
2004-12-27 13:00 ` Paulo Marques
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=20050125055218.GA15014@trane.bluesong.net \
--to=jfv@bluesong.net \
--cc=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanan.mainker@gmail.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
Powered by JetHome