[snip] > Even if that isn't the problem, you should probably declare those > variables static so that future readers of the code don't have to go > looking to find out where else the variables might be used or changed. Although I agree that static declarations are a better idea, it's unlikely to be relevant to the problem at hand.
The code in question is a kernel module, which means two things regarding variable scope: 1) the symbol isn't available to other modules unless explicitly exported with EXPORT_SYMBOL; 2) it's a kernel module, which means that it can scribble on anything, or be scribbled on by any other kernel module. That is somewhat different in sim though, which could be at least a part of why it works differently in sim vs. RT. - Steve ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
