lkml.org 
[lkml]   [2007]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2.6.21] cramfs: add cramfs Linear XIP
    > An alternative approach, which does not need to have struct page at
    > hand, would be to use the nopfn vm operations struct. That one would
    > have to rely on get_xip_pfn.

    Of course! Okay now I'm begining to understand.

    > The current path would then be deprecated.

    Why? Wouldn't both paths be valid options?

    > If you're interrested in using the later for xip without
    > struct page, I would volounteer to go ahead and implement this?

    I'm very interested in this.


    I'm not opposed to using struct page, but I'm confused as to how to
    start that. As I understand it, which is not well, defined a
    CONFIG_DISCONTIGMEM region to cover the Flash memory would add that to
    my pool of RAM. That would be 'bad', right? I don't see how to
    create the page structs and set this memory aside as different.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-06-14 18:55    [W:3.469 / U:0.892 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site