2013-12-05, 16:30
@MilhouseVH
Can you please confirm if this commit of 5 days ago was included in your latest build (r16483) or not.
If it was included then I'm afraid it didn't bring the gpio receiver back to life as I would have hoped (unless we're meant to make any changes to the autostart.sh file).
If it wasn't included, I assume your next build will?
EDIT: forget all this - the lirc_rpi.c is the same as in previous versions. I guess I just got excited when I saw a recent commit that was related to the gpio receiver.
EDIT2: perhaps don't forget
It looks as though for all versions back to 3.10.y, this commit was only made 5 days ago. In addition, I see that there were other changes made recently i.e. "lirc_rpi: Don't register with lirc_dev if we can't claim gpio pins" - I wonder if this could be a timing issue with registering the driver if it doesn't "claim the gpio pins" quickly enough?
Can you please confirm if this commit of 5 days ago was included in your latest build (r16483) or not.
If it was included then I'm afraid it didn't bring the gpio receiver back to life as I would have hoped (unless we're meant to make any changes to the autostart.sh file).
If it wasn't included, I assume your next build will?
EDIT: forget all this - the lirc_rpi.c is the same as in previous versions. I guess I just got excited when I saw a recent commit that was related to the gpio receiver.
EDIT2: perhaps don't forget
It looks as though for all versions back to 3.10.y, this commit was only made 5 days ago. In addition, I see that there were other changes made recently i.e. "lirc_rpi: Don't register with lirc_dev if we can't claim gpio pins" - I wonder if this could be a timing issue with registering the driver if it doesn't "claim the gpio pins" quickly enough?
