From: Jens Axboe <jens.axboe@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Geoff Levand <geoffrey.levand@am.sony.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Jim Paris <jim@jtan.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 07:54:23 +0100 [thread overview]
Message-ID: <20090305065423.GK11787@kernel.dk> (raw)
In-Reply-To: <1236209255.6696.75.camel@pasglop>
On Thu, Mar 05 2009, Benjamin Herrenschmidt wrote:
> On Wed, 2009-03-04 at 14:57 +0100, Geert Uytterhoeven wrote:
> > Hi,
> >
> > Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> > device, as requested by Arnd Bergmann.
> >
> > The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> > kernel in 2.6.29-rc1.
> >
> > Ideally, we think it would be best if the existing MTD-based ps3vram driver
> > would be replaced by the new block-based ps3vram driver before 2.6.29 is
> > released. This would relieve the burden of supporting two different swap space
> > schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> > maintainer's shoulders, as in that case there would never have been a stable
> > kernel version containing the MTD-based ps3vram driver.
>
> This is very very very late ... we are at rc7, probably one rc before
> final... as much as I like integrating drivers later, I'll ask Linus
> opinion on this one.
>
> Linus ? What do you reckon ? Maybe a better option is just to remove
> ps3nvram from .29 and merge the new one in .30 ?
It's an isolated driver for a special purpose platform, I would have
zero problems merging it :-)
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Jim Paris <jim@jtan.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 07:54:23 +0100 [thread overview]
Message-ID: <20090305065423.GK11787@kernel.dk> (raw)
In-Reply-To: <1236209255.6696.75.camel@pasglop>
On Thu, Mar 05 2009, Benjamin Herrenschmidt wrote:
> On Wed, 2009-03-04 at 14:57 +0100, Geert Uytterhoeven wrote:
> > Hi,
> >
> > Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> > device, as requested by Arnd Bergmann.
> >
> > The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> > kernel in 2.6.29-rc1.
> >
> > Ideally, we think it would be best if the existing MTD-based ps3vram driver
> > would be replaced by the new block-based ps3vram driver before 2.6.29 is
> > released. This would relieve the burden of supporting two different swap space
> > schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> > maintainer's shoulders, as in that case there would never have been a stable
> > kernel version containing the MTD-based ps3vram driver.
>
> This is very very very late ... we are at rc7, probably one rc before
> final... as much as I like integrating drivers later, I'll ask Linus
> opinion on this one.
>
> Linus ? What do you reckon ? Maybe a better option is just to remove
> ps3nvram from .29 and merge the new one in .30 ?
It's an isolated driver for a special purpose platform, I would have
zero problems merging it :-)
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Jim Paris <jim@jtan.com>,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Geoff Levand <geoffrey.levand@am.sony.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 07:54:23 +0100 [thread overview]
Message-ID: <20090305065423.GK11787@kernel.dk> (raw)
In-Reply-To: <1236209255.6696.75.camel@pasglop>
On Thu, Mar 05 2009, Benjamin Herrenschmidt wrote:
> On Wed, 2009-03-04 at 14:57 +0100, Geert Uytterhoeven wrote:
> > Hi,
> >
> > Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> > device, as requested by Arnd Bergmann.
> >
> > The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> > kernel in 2.6.29-rc1.
> >
> > Ideally, we think it would be best if the existing MTD-based ps3vram driver
> > would be replaced by the new block-based ps3vram driver before 2.6.29 is
> > released. This would relieve the burden of supporting two different swap space
> > schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> > maintainer's shoulders, as in that case there would never have been a stable
> > kernel version containing the MTD-based ps3vram driver.
>
> This is very very very late ... we are at rc7, probably one rc before
> final... as much as I like integrating drivers later, I'll ask Linus
> opinion on this one.
>
> Linus ? What do you reckon ? Maybe a better option is just to remove
> ps3nvram from .29 and merge the new one in .30 ?
It's an isolated driver for a special purpose platform, I would have
zero problems merging it :-)
--
Jens Axboe
next prev parent reply other threads:[~2009-03-05 7:01 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:57 [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device Geert Uytterhoeven
2009-03-04 13:57 ` Geert Uytterhoeven
2009-03-04 13:57 ` Geert Uytterhoeven
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-05 6:54 ` Jens Axboe [this message]
2009-03-05 6:54 ` Jens Axboe
2009-03-05 6:54 ` Jens Axboe
2009-03-06 12:54 ` [PATCH] ps3/block: Replace mtd/ps3vram by block/ps3vram (was: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device) Geert Uytterhoeven
2009-03-06 12:54 ` Geert Uytterhoeven
2009-03-06 12:54 ` Geert Uytterhoeven
2009-03-09 17:51 ` [PATCH] ps3/block: Replace mtd/ps3vram by block/ps3vram Geoff Levand
2009-03-09 17:51 ` Geoff Levand
2009-03-05 0:21 ` [Cbe-oss-dev] [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device Marcus G. Daniels
2009-03-05 0:21 ` Marcus G. Daniels
2009-03-05 0:21 ` Marcus G. Daniels
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 18:12 ` Olaf Hering
2009-03-05 18:12 ` Olaf Hering
2009-03-05 18:12 ` Olaf Hering
2009-03-05 8:37 ` Jens Axboe
2009-03-05 8:37 ` Jens Axboe
2009-03-05 8:37 ` Jens Axboe
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 11:09 ` Jens Axboe
2009-03-05 11:09 ` Jens Axboe
2009-03-05 11:09 ` Jens Axboe
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-06 7:46 ` Jens Axboe
2009-03-06 7:46 ` Jens Axboe
2009-03-06 7:46 ` Jens Axboe
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:58 ` Jens Axboe
2009-03-06 12:58 ` Jens Axboe
2009-03-06 12:58 ` Jens Axboe
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 19:03 ` Jens Axboe
2009-03-06 19:03 ` Jens Axboe
2009-03-06 19:03 ` Jens Axboe
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:58 ` Jens Axboe
2009-03-09 10:58 ` Jens Axboe
2009-03-09 10:58 ` Jens Axboe
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=20090305065423.GK11787@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=geoffrey.levand@am.sony.com \
--cc=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=torvalds@linux-foundation.org \
--cc=vivien.chappelier@free.fr \
/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.