Lennert Buytenhek <[EMAIL PROTECTED]> writes: > The way I see it, that means that you do want to scale back your > other SRAM allocations if you know that you're going to need a lot > of SRAM (say, for ethernet RX/TX queues.)
Yep, I will then add "queue_size" parameter to the platform data. Or something like that. > Or you can put this knowledge in the board support code (cleaner, IMHO.) Sure. > That way, you can _guarantee_ that you'll always have enough SRAM > to be able to use the functionality that is exposed on the board you > are running on (which is a desirable property, IMHO), which is > something that you can't achieve with an allocator, as far as I can > see. I'd have to put SRAM address in the board code instead. Certainly not required at this point, and perhaps it will be never needed. -- Krzysztof Halasa - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
