Re: linux-2.6_2.6.39-1_amd64.changes ACCEPTED into unstable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Geert,

On Tue, Jun 14, 2011 at 6:49 AM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
On Mon, May 30, 2011 at 19:22, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote:
On Mon, May 30, 2011 at 19:14, Michael Schmitz
<schmitzmic@xxxxxxxxxxxxxx> wrote:
remind me - what rewrite will be required?

Remove your own memory allocator.
Probably the simplest is to always reserve some ST-RAM on bootup, and let
stram_alloc()/stram_free() use that reserved pool.

I've seen your work on the chip RAM driver, will take a close look at
adapting this for ST-RAM when I return from overseas.

When will you return, just in case I come to it before that (woow, I
feel overly optimistic now)?

Has anyone besides me tried http://lkml.org/lkml/2011/6/5/46 on top of
https://lkml.org/lkml/2011/5/21/142?

Sorry, I haven't had much time to do any coherent work on this yet. I
seem to have fried my EtherNAT PHY, two of my SCSI disks didn't come
back up after I returned from overseas, and I have been just too
jetlagged to risk blowing up anything else.

I do very much appreciate your effort in getting rid of the old ST-RAM
allocator, and I will try to test a new kernel later this week.

Cheers,

  Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux