mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: James Simmons <jsimmons@www.infradead.org>
Cc: linux-mips@linux-mips.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: TurboChannel Bsus sysfs port.
Date: Sat, 22 Jan 2005 17:04:07 +0100	[thread overview]
Message-ID: <20050122160407.GT28037@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.56.0501220021540.1021@pentafluge.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Sat, 2005-01-22 00:25:28 +0000, James Simmons <jsimmons@www.infradead.org>
wrote in message <Pine.LNX.4.56.0501220021540.1021@pentafluge.infradead.org>:
> 
> Experimenting with sysfs to figure out how it works. So I'm attempting to 
> port the TurboChannel bus code to sysfs. Its a test of concept and a 
> learning experience. Comments welcomed.
[...]

I haven't tested the code, but basically, it's a good step into the
right direction. The DECstations aren't yet really in the 2.6.x world,
but that doesn't degrade your good work :-)  Also, it now seems easier
to me to integrate a different TC bus driver: this will be needed for
Linux' port to VAX computers, which may have TC busses, too.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-01-22 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22  0:25 James Simmons
2005-01-22 16:04 ` Jan-Benedict Glaw [this message]

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=20050122160407.GT28037@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=jsimmons@www.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.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

all inboxes | Powered by JetHome®