From: Olaf Hering <olaf@aepfle.de>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jens Axboe <axboe@kernel.dk>, Jim Paris <jim@jtan.com>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
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 08:17:24 +0100 [thread overview]
Message-ID: <AA44F8E7-5FBC-4378-A86D-C094ECABD625@aepfle.de> (raw)
In-Reply-To: <alpine.LRH.2.00.0903041444300.32279@vixen.sonytel.be>
Am 04.03.2009 um 14:57 schrieb Geert Uytterhoeven:
> 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.
openSuSE already ships with the ps3vram driver since a two releases.
A simple name based udev rule could symlink ps3vram to mtdblock0, so
an upgrade
will not break existing setups.
> +obj-$(CONFIG_PS3_VRAM) += ps3vram_ng.o
Please give the driver the obvious name "ps3vram", that way upgrading
will be smooth.
I see our old mtddriver does not have modalias support for autoloading.
Hopefully the new driver has this feature.
Olaf
next prev parent reply other threads:[~2009-03-05 7:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:57 Geert Uytterhoeven
2009-03-04 23:27 ` Benjamin Herrenschmidt
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-09 17:51 ` [PATCH] ps3/block: Replace mtd/ps3vram by block/ps3vram 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 7:17 ` Olaf Hering [this message]
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 18:12 ` Olaf Hering
2009-03-05 8:37 ` Jens Axboe
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 11:09 ` Jens Axboe
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-06 7:46 ` Jens Axboe
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:58 ` Jens Axboe
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 19:03 ` Jens Axboe
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:52 ` Geert Uytterhoeven
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=AA44F8E7-5FBC-4378-A86D-C094ECABD625@aepfle.de \
--to=olaf@aepfle.de \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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 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®