@xenic
please note there was an error in the labelling of the sensor, please use the new version of my docky from OS4Depot (or via AmiUpdate).
Search found 159 matches
- Tue Apr 16, 2013 12:12 pm
- Forum: Platform: AmigaOne X1000
- Topic: Hot or not
- Replies: 16
- Views: 7216
- Thu Mar 21, 2013 6:40 pm
- Forum: Platform: AmigaOne X1000
- Topic: Sometimes the X1000 doesn't boot [SOLVED]
- Replies: 156
- Views: 108465
Re: Sometimes the X1000 doesn't boot
@xeno74 I don't know if it means anything but your ETH0_HWADDR variable is a little different than mine, which is: ETH0_HWADDR=00:50:C2:20:DA:44 Yours has a different last number for the address. That's normal this is the MAC address of his motherboard. This is supposed to be unique... worldwide. S...
- Fri Mar 15, 2013 2:53 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
By the why do you want to put your driver as a Kickstart module?
- Fri Mar 15, 2013 2:09 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
The problem starts as soon as I use XeroMouse as Kickstart module. Its based on the rMouse driver, so nothing special here, besides the Expunge problem, which is eliminated as cause now. Hmm, maybe there is something special to setup in order to be used as a Kickstart module, I don't know. I'll try...
- Fri Mar 15, 2013 12:12 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
Ok so now that you have a serial debug setup, can you try to type in a shell : newshell <>TCP:12345 this should let you have a shell waiting for input on TCP port 12345 (just an example port number, choose what you want, beware reusing standard port though) After that try on the remote computer to c...
- Fri Mar 15, 2013 9:32 am
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
@whose No you don't *need* to change anything in UBoot: it's just easier to have it setup automatically there rather than being obligated to set it via a shell at each boot (you can use the user-startup though ;-) Look at the kdebug command line options in your SYS:Documentation drawer. No my tablet...
- Thu Mar 14, 2013 4:42 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
There is information in the autodocs which state you must Obtain/Release every Interface you use for each Task/Process. I'm not near my Amiga right now, but IIRC looking for an Obtain or Release section in the autodocs one would not find anything. It seems to me the documentation is located in the ...
- Thu Mar 14, 2013 3:14 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
@whose By any chance do you have a serial cable that would be able to capture your crash? It would be really odd that hid.usbfd would cause problem to your driver while it does not on mine... (Note that without an adapted driver a Wacom device will still be recognized as an HID mouse and work in a r...
- Thu Mar 14, 2013 2:35 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
Here is the code from my WacomDriver which I can plug/unplug at will without any crash /* Expunge the library */ APTR _manager_Expunge( struct LibraryManagerInterface *Self ) { struct WacomTabletBase *libBase; APTR result; libBase = (struct WacomTabletBase *)Self->Data.LibBase; if ( libBase->rmb_Ope...
- Thu Mar 14, 2013 12:48 pm
- Forum: General Developer Support
- Topic: XeroMouse & hid.usbfd could co-exist?
- Replies: 27
- Views: 13522
Re: XeroMouse & hid.usbfd could co-exist?
@whose It's a bug in the (rmouse) code of the Expunge routine. ReRead it carefully and you'll notice that it is accessing some libBase member after it has deleted it... That's BAD ;-) I should probably modify and upload a fixed version of the rMouse driver so that no one else comes to this problem a...