ev64260 bi_rec patch
Quoted 2 lines · Paul Mackerras
Use the memory pointed to by klimit and increment klimit by the amount you use. You should keep klimit aligned on a 4-byte boundary, I think.
Yeah, I've already figured this out myself by looking at what you do for OF.
I'm working on one really big changeset right now that'll add a CONFIG_GENERIC_PPC32 configuration, have presistent and searchable bi_recs, a new and much cleaner GT-64260 implementation, etc. I'll push it into linuxppc_2_4_alt when it's ready to see the light of day (hopefully tomorrow or Wednesday).
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 5 lines · Michael Sokolov
Quoted 2 lines · Paul Mackerras
Use the memory pointed to by klimit and increment klimit by the amount you use. You should keep klimit aligned on a 4-byte boundary, I think.
Quoted 7 lines
Yeah, I've already figured this out myself by looking at what you do for OF.
I'm working on one really big changeset right now that'll add a
CONFIG_GENERIC_PPC32configuration, have presistent and searchablebi_recs, a new and much cleaner GT-64260 implementation, etc. I'll push it intolinuxppc_2_4_altwhen it's ready to see the light of day (hopefully tomorrow or Wednesday).
Would you mind detailing exactly what's in your 'much cleaner' gt64260 implementation? Like, do you have an SMP-safe gt ethernet driver perchance? ;)
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | [email protected] -----"If this message isn't misspelled, I didn't write it" -- Me ----- "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Schulz
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/