Ah, ok. Next up then is finding out about this magical "inserting modules into the kernal" of which you speak. This is good for my resume I'm sure. On Thu, Sep 11, 2014 at 6:00 PM, Chris Osborn <fozztexx@fozztexx.com> wrote: > The /dev/iec8 device will be created when you insert the module into the > kernel. If it's not there, creating it from your userspace program won't > help. > > Sorry, I didn't see the message that came by earlier. > > On Sep 11, 2014, at 3:55 PM, Rob Eaglestone <robert.eaglestone@gmail.com> > wrote: > > Ah, problem solved by simply changing the open() command args: > > dosfd = open("/dev/iec8", O_RDWR | O_CREAT ); > > Duh. > > > On Thu, Sep 11, 2014 at 7:19 AM, Rob Eaglestone < > robert.eaglestone@gmail.com> wrote: > >> I had to install the wiringPi library (you should mention that in the >> README), and then alter the makefile (-lobjc causes make to fail) and >> remove the joystick references in ninepin.c (because it relies on >> /usr/src/linux/include/linux/asm, which doesn't exist in my distribution >> for some reason). >> >> Then it compiled. >> >> And now for a newbie question on linux hacking: >> >> How do I run this thing? Running 'sudo ./ninepin' results in an error, >> because it can't open /dev/iec8 ("no such file or directory"). >> >> So do I need to create /dev/iec8? And do I use something like MAKEDEV or >> mknod, or something else? >> >> >> >> On Thu, Sep 4, 2014 at 8:12 PM, Rob Eaglestone < >> robert.eaglestone@gmail.com> wrote: >> >>> OK. Before I dive in, I'll tell you that one of the things I aim to do >>> is write a library, not unlike the BCM2835 one, and from there produce a >>> Perl package that can access that library, not unlike Device::BCM2835 >>> <https://metacpan.org/pod/Device::BCM2835>. So if that brings any >>> advice to mind, I'm all ears :) >>> >>> >>> >>> On Thu, Sep 4, 2014 at 6:42 PM, Chris Osborn <fozztexx@fozztexx.com> >>> wrote: >>> >>>> >>>> On Sep 4, 2014, at 4:20 PM, Rob Eaglestone <robert.eaglestone@gmail.com> >>>> wrote: >>>> >>>> > Thanks Chris! (And Nate!) >>>> > >>>> > Between my initial email and yours, I had functions written but no >>>> certainty that they'd work. I'll hack on your codebase instead. >>>> >>>> Easiest thing to do would be to start from cbmdos & dosHandleIO. When >>>> that's called all of the low-level protocol things have been taken care of >>>> and all you have to do is read in a buffer which will tell you the command >>>> that is being sent. >>>> >>>> -- >>>> Follow me on twitter: @FozzTexx >>>> Check out my blog: http://insentricity.com >>>> >>>> >>>> Message was sent through the cbm-hackers mailing list >>>> >>> >>> >> > > Message was sent through the cbm-hackers mailing listReceived on 2014-09-12 01:00:03
Archive generated by hypermail 2.2.0.