Osst needs updating Xnxx p

Dear all, I'm trying to use my USB mass storage (8GB USB memory stick) on Android. In other words, is it possible (at all) to upload these same images to, say, a G1 phone and expect the same behavior I see in the emulator to be on the G1 phone (assuming of course I use a cross-compiler for that target phone to build the *files).

osst needs updating-54osst needs updating-3osst needs updating-78

============================================== /proc # cat interrupts CPU0 3: 42 SC ohci_hcd:usb1 17: 2 SC LCD 22: 134 SC FFUART 23: 11 SC pxa2xx- mci 25: 0 SC DMA 26: 3341 SC ost0 192: 0 FPGA MMC card detect Err: 0 ================================ /proc # cat partitions major minor #blocks name 31 0 256 mtdblock0 31 1 4096 mtdblock1 31 2 28416 mtdblock2 8 0 8192 sda [android-porting] Re: sensor HAL in cupcake Hi, Check the values configured for the following build vars: 1. ro.board.platform Apparently one of these vars got configured with the string "myproject", you need to reconfigure that to a valid string (appropriate for the target device) Warm Regards, Anil On Fri, Feb 20, 2009 at PM, pramod gurav --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: -~----------~----~----~----~------~----~------~--~--- Girish --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: -~----------~----~----~----~------~----~------~--~--- [android-porting] Questions on ramdisk, userdata, and system img files Hi, I'm new to Android development and recently I've been playing with the emulator and the applications, etc, and overall just getting to know the internals of the code. The messages below are that I ran after kernel is booted up.Or are these img files solely for emulator-purposes only?I apologize if this is too elementary for you guys as I'm learning along the way here.Any input about those img files are greatly appreciated.

I have a Quantum Superloader 3 LTO-4 SAS I'm trying to setup under Ubuntu Server 8.04.1 64-bit. I'm having a hard time coming by anyone that's used an autoloader under Ubuntu. Results of cat /proc/scsi/scsi: Host: scsi0 Channel: 00 Id: 32 Lun: 00 Vendor: DP Model: BACKPLANE Rev: 1.05 Type: Enclosure ANSI SCSI revision: 05 Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: DELL Model: PERC 6/i Rev: 1.11 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: TEAC Model: CD-ROM CD-224E-N Rev: 3.

AC Type: CD-ROM ANSI SCSI revision: 05 Host: scsi3 Channel: 00 Id: 01 Lun: 01 Vendor: ETIUSA Model: E500 Rev: 2.2.

Type: Direct-Access ANSI SCSI revision: 04 Host: scsi3 Channel: 00 Id: 02 Lun: 00 Vendor: QUANTUM Model: ULTRIUM 4 Rev: 2143 Type: Sequential-Access ANSI SCSI revision: 05 I think my first goal should be making sure it recognizes the autoloader, not just the drive.

From there, I know I need to configure /etc/stinit.def, but I have no clue how to approach that. I'm not sure PERC5s are designed to run tape drives, they're RAID cards.

In the HP world you have to use plain-jane SCSI cards rather than their RAID controllers to run an autoloader (the documentation explicitly says 'don't use the RAID card').

My interpretation of that link is that the card is designed to work with disk enclosures, not autoloaders.