On 11/4/2013 1:18 PM, Aaron J. Seigo wrote:
On Monday, November 4, 2013 12:43:16 Christopher Havel wrote:
What I want to do with it is run FatDogARM, which is a version of Puppy
cool. sounds quite useful and interesting.
i didn’t actually mean for you to post your project here directly, but i appreciate that you did.
Well, I thought you might not be the only one who would want to hear it. Consider it also a partial introduction for me ;) I'm a Puppian for sure, although I'm not certainly not representing Puppy in any official capacity! By the way, I'm also a community dev with Puppy -- I created a Puplet for artists, that I'm sort of maintaining, called Vincent Van Pup ("sort of" because I need to mix up the next revision and I keep dang procrastinating...). *truly shameless plug* the thread for that Puplet (Vinnie, for short :P ) is here, if there's any interest at all --> http://murga-linux.com/puppy/viewtopic.php?t=89395
thinks it'll be a cakewalk. I'm not 100% sure, mostly because of that EEPROM and the fact that I can't compile.
the EEPROM doesn’t interfere with anything; you can happily ignore it as much as you want.
It's not "interference" that I'm concerned about with the EEPROM. It's an interface issue -- how does an OS, eg FatDogARM, "know" that the EEPROM is there, read the contents, and act accordingly...? I know that ARM is largely un-autoprobe-able...