Geert Uytterhoeven dixit:
>> Furthermore, we just wanted to use the BigRAMPlus as a swap device
>> now following Ingo's description [1]. Unfortunately, CONFIG_MTD
>> is not set in the current Debian m68k kernel and we therefore
>> can't use it.
>>
>> Any chance we can activate that?
>
>Build your own kernel?
Either that, or ask the Debian kernel maintainers to enable that
symbol for us. If it’s already enabled in other architectures,
this may be done as-is; otherwise, they may want to enable it
generically, which will need to wait until after the unblock.
>But I think a real block device driver would perform better.
>drivers/block/ps3vram.c would be a good example.
Or that, sure.
But I think that, if the kernel source is going to be changed
at all, using it as RAM straight would be better, since more
RAM means not only less need to swap but also better RAM use
and all that.
bye,
//mirabilos
PS: Who’s going to write a report about the weekend? Not me…
but having one would be nice ☺
--
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design. <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/pine.bsm.4.64l.1501181517170.24...@herc.mirbsd.org
