All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aubin LaBrosse <arl8778@rit.edu>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Jeff Garzik <jgarzik@pobox.com>, Matt Mackall <mpm@selenic.com>,
	Jens Axboe <axboe@suse.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Worrisome IDE PIO transfers...
Date: Sun, 29 Feb 2004 04:32:23 -0500	[thread overview]
Message-ID: <1078047142.5232.41.camel@rain.rh.rit.edu> (raw)
In-Reply-To: <200402290408.12917.bzolnier@elka.pw.edu.pl>

On Sat, 2004-02-28 at 22:08, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 29 of February 2004 03:41, Jeff Garzik wrote:
> > Matt Mackall wrote:
> > > On Sun, Feb 29, 2004 at 01:21:30AM +0100, Bartlomiej Zolnierkiewicz wrote:
> > >>I like Alan's idea to use loopback instead of "bswap".
> > >
> > > Or, more likely, device mapper.
> >
> > Somehow I doubt anybody cares enough to write a whole driver just for
> > this unlikely case.
> 
> Any TiVo hacker reading this? :)
> 

ahem.  now for the whole list instead of just Bart, (sorry Bart) in case
any of you gurus have insights for me (even if it's just to tell me I'm
biting off more than I can chew.)

I'm definitely reading, but not necessarily comprehending.  I upgraded a
60GB TiVo to 2x80GB in about 2002 using 2.4 and some userland tools.  in
fact i was just contemplating doing another upgrade since the 80s in it
now are on their way out i think, so i'll even have some spare TiVo
drives to fool around with during the development of this thing. I'm
probably not qualified to begin an undertaking like this, I'm just a
student, but....I've always wanted to be a kernel hacker. ;-) but i'm
not sure I understand what would be involved. And, does this mean I'll
have to use 2.4 to do my next upcoming drive replacement? (replacing the
drives in the tivo requires a host linux box on which to do it)

If someone would be kind enough to give me a little more info about the
dm driver for tivo drives, i'd at least entertain the idea...

-Aubin



  reply	other threads:[~2004-02-29  9:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 23:24 Worrisome IDE PIO transfers Jeff Garzik
2004-02-29  0:21 ` Bartlomiej Zolnierkiewicz
2004-02-29  0:58   ` Jeff Garzik
2004-02-29  3:05     ` Bartlomiej Zolnierkiewicz
2004-02-29  8:52       ` Geert Uytterhoeven
2004-02-29 19:23         ` Richard Zidlicky
2004-02-29 20:36           ` Bartlomiej Zolnierkiewicz
2004-03-01 10:43             ` Richard Zidlicky
2004-02-29  1:50   ` Matt Mackall
2004-02-29  2:41     ` Jeff Garzik
2004-02-29  3:08       ` Bartlomiej Zolnierkiewicz
2004-02-29  9:32         ` Aubin LaBrosse [this message]
2004-03-01  0:47       ` Bartlomiej Zolnierkiewicz
2004-03-01 13:23         ` Christophe Saout
2004-03-01 16:45           ` Bartlomiej Zolnierkiewicz
2004-02-29  8:50   ` Geert Uytterhoeven
2004-02-29 14:55     ` Bartlomiej Zolnierkiewicz

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=1078047142.5232.41.camel@rain.rh.rit.edu \
    --to=arl8778@rit.edu \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=axboe@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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 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.