**** BEGIN LOGGING AT Wed Oct 10 02:59:57 2007
Oct 10 13:40:30 <prpplague> morning all
Oct 10 13:40:38 <prpplague> drath: whats cookin today?
Oct 10 14:35:25 <prpplague> drath: i really think that nand.c should be totally ignorant of the buswidth of the nand flash
Oct 10 14:36:34 <drath> hey prpplague 
Oct 10 14:36:55 <prpplague> drath: greetings
Oct 10 14:37:06 <prpplague> drath: beer-thirty there yet?
Oct 10 14:38:18 <drath> prpplague: imho every hour with a "pm" qualifies for that ;)
Oct 10 14:38:19 <prpplague> drath: imho all the data i/o from within nand.c should be done as u32, the controller code, i.e. the lpc3180 or s3c24xx should handle the proper breakdown of the data
Oct 10 14:38:24 <prpplague> drath: hehe
Oct 10 14:38:27 <prpplague> drath: good deal
Oct 10 14:45:30 <drath> prpplague: well, in case of a manufacturer id read for example, we want exactly one bus-size data word - what would you return in that case?
Oct 10 14:46:57 <drath> a 32-bit read could hold 2x16bit or 4x8bit - we need to know that bus-width to know what that data is
Oct 10 14:47:06 <prpplague> drath: i'd still return a u32, just have some code to break out the ids
Oct 10 14:47:33 <prpplague> drath: hmm
Oct 10 14:48:21 <prpplague> drath: the problem i have is that even though this is a 8-bit buswidth, all the access to it is designed around operations doing x32
Oct 10 14:50:04 <prpplague> drath: i'll tinker around some more, but i still think the nand.c data i/o should be x32 and let the controller code do the actually low level buswidth control
Oct 10 14:50:50 <drath> prpplague: heh, feel free to propose a patch that works for you and i'll have a look at it
Oct 10 14:53:27 <prpplague> drath: will do, still testing and tinkering
Oct 10 14:53:39 <prpplague> drath: just thought i'd break the ice on the topic
Oct 10 14:54:49 <prpplague> drath: a good example for me is the fact that the address function call doesn't know if it it needs one write or four
Oct 10 14:55:00 <prpplague> drath: thats handled in the controller code
Oct 10 14:55:17 <prpplague> drath: i.e. in my s3c24xx code i do one x32 write
Oct 10 14:56:03 <drath> prpplague: if this is only about performance: that's what the ->read_page and ->write_page functions are for
Oct 10 14:56:51 <drath> prpplague: the controller is free to do whatever it wants in that case, it should just return the data
Oct 10 14:57:07 <prpplague> drath: it is only partly related to performance
Oct 10 21:56:43 <prpplague> drath: ping
Oct 10 21:57:01 <prpplague> drath: nm
Oct 10 21:57:06 <prpplague> unping
Oct 11 00:39:16 <flyback> anyone done serial over ethernet
**** ENDING LOGGING AT Thu Oct 11 02:59:56 2007