[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <AA44F8E7-5FBC-4378-A86D-C094ECABD625@aepfle.de>
Date: Thu, 5 Mar 2009 08:17:24 +0100
From: Olaf Hering <olaf@...fle.de>
To: Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Jens Axboe <axboe@...nel.dk>, Jim Paris <jim@...n.com>,
Arnd Bergmann <arnd@...db.de>,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
Linux/PPC Development <linuxppc-dev@...abs.org>,
linux-mtd@...ts.infradead.org,
Vivien Chappelier <vivien.chappelier@...e.fr>,
David Woodhouse <dwmw2@...radead.org>,
Cell Broadband Engine OSS Development
<cbe-oss-dev@...abs.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists