On 11/14/2010 3:59 PM, Dong, Chuanxiao wrote:
my first impression is that it's all much too complex.
(and block changes need to go to the block layer people not the mmc people)
No, the block layer I mean is the MMC driver block layer, mmc people own this.
It is not the kernel block layer. I didn't change any kernel block layer code.
why not pick 128 or 256 or some reasonable number, rather than doing
extremely complex and fragile calculations??
Since I want my host controller can handle the maximum sectors at one time. I
think the value calculated is much reasonable than some other value. So, you
mean I can just pick some value like 128 or 256 rather than some calculated
value?
I think what you are doing is too complex; you're working around a
silicon bug... the rule is Keep It Simple.
also, can you make sure this is internally filed as a sighting so that
it'll get fixed in the next stepping?
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
