Puppy Linux Discussion Forum

nibl · Joined: 07 Dec 2006 Posts: 103

Can anybody help connecting an Android device to Puppy for development?

(This allows the device to be connected via USB in debug mode. The Android SDK can then install apps during development directly to the device.)

On Lupu 525, lsusb lists the device. I tried the udev rule provided by the manufacturer, but the device is not seen by Puppy. There have been two threads in the past, but so far no solution. We need somebody with in-depth knowledge of Puppy. This is presumably either a udev or kernel issue. It works on Ubuntu.

Here's the official doc page:

http://developer.android.com/guide/developing/device.html#setting-up

Many Thanks, I really want to use Puppy for development and not Ubuntu.

Marcus

nooby · Joined: 29 Jun 2008 Posts: 9385 Location: SwedenEurope

is not the SDK excusively for Ms Windows? And if it is for Linux it may not run as root or Puppy needs to do a sfs or pet out of that one?

Have you used the search engine in my link to see what others have written about their attempts to do the same?

Just me curious. I wish me could do such things but have not tried yet

nibl · Joined: 07 Dec 2006 Posts: 103

Karl Godt · Joined: 20 Jun 2010 Posts: 2675 Location: Kiel,Germany

udev checks the sys directory for entries . If one entry changes , it recognizes this .

The udev rule is for "what should udev do next ?"

I have and older Suse Linux with kernel 2.29 I think extracted once to USB and the rule was simple to understand : it yust would do a /sbin/modprobe to load the desired driver(s) automatically .

If you know the driver name , you could do it manually in the console window or put a short script into $HOME/Startup .

Puppy uses the udev rules at bootup to echo a keyword into the drivers file(s) named uevent in all the /sys sub-directories . When udevd detects the keyword it will run /sbin/pup_event_backend_modprobe which is a script to handle driver options , alsa and firmwares and wrong modules.dep entries before it loads the driver using the /sbin/modprobe command at the very end .
The uevent file gets restored immediately to its previous state and enrties , like

cat /sys/devices/pnp0/00:09/uevent
DRIVER=serial

Some uevent files are larger and some are not cat'able .

Instead of loading a driver by 'modprobe DRIVER' you could also do a 'pup_event_backend_modprobe DRIVER' manually .

Puppys' bootscript '/etc/rc.d/rc.sysinit' collects
MODALIASES="`ls /sys/bus/*/devices/*/modalias`"
files that are written by the kernel , before any other external compiled drivers got loaded at full installations .

If the kernel is not able to detect anything for the hardware , thus not writing any files somewhere in /sys/path/to/DRIVERNAME , it maybe because this hardware is not supported by the kernel-version ( too ^old^ ) , it should be compiled with different options , or is not compiled as a driver at all ( because of the size of the .iso - or whatever ) .

nibl · Joined: 07 Dec 2006 Posts: 103

Karl, Thanks for all the info. I'm not sure how to find the device though.

All I know is that "lsusb" sees the device (e.g. "Bus 001 Device 006: ID xxxx:yyyy"). The manufacturer's ID I get is correct.

The device can also be mounted, that is, Puppy shows the icon on the desktop and files can be copied. However, that is file transfer mode and development/debug mode is different and possibly uses a different driver. Is there any way I can use that info so Puppy can talk to the device?