Re: A910 and boot_usb

[Marc Bobillier]

* Paulo Marques [2007-06-06 11:50:30 +0100]:
> If you see green text messages you probably have the same problem I have 
> with the ROKR E6: the framebuffer is 18bpp and not 16bpp.

Yes, A910 is 256k colors.

-- 
marc

Re: A910 and boot_usb

[Marc Bobillier]

* Daniel Ribeiro [2007-06-04 18:10:46 -0300]:
> A typo broke boot_usb for e2, e6, a1200 and a910.
> Its fixed on r2025, please try again.

It boots now! I get a muticolor garbage screen, then tux logo and
scrolling green kernel messages, then panic :-)

Next step : booting a 2.6.21 kernel.

Thanks
-- 
marc

A910 and boot_usb

[marc]

Hi all,

Here is my attempt at booting a zImage on a A910 :

# ./boot_usb zImage-2.6.13-ezx6-32mb-p1
E2/A1200/E6 found.
TX: RQSN ( 02 52 51 53 4e 03)
TX: RQVN ( 02 52 51 56 4e 03)
TX: ADDRA0DEBA ( 02 41 44 44 52 1e 41 30 44 45 30 30 30 30 42 41 03)
TX: JUMPA0DEBA ( 02 4a 55 4d 50 1e 41 30 44 45 30 30 30 30 42 41 03)
#

boot_usb was downloaded and compiled today, and run as root.

Here is lsusb 0.1.12 output with the A910 in bootloader mode :

Bus 001 Device 005: ID 22b8:6023 Motorola PCS 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize016
  idVendor   0x22b8 Motorola PCS
  idProduct  0x6023 
  bcdDevice0.01
  iManufacturer   1 
  iProduct2 
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   32
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  4 
bmAttributes 0xc0
  Self Powered
MaxPower   10mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass 10 
  bInterfaceProtocol255 
  iInterface  5 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0

regards
-- 
marc

Re: How to tell the return code of functions?

[Marc de Courville]

Michael,

According to Michael Lachmann <[EMAIL PROTECTED]> (on 04/17/07):
> I am trying to write a perl script that will take the output of
> arm-linux-nm -aDC
> and
> arm-linux-objdump -T --demangle
> and produce .h files. (For the A1200)
> 
> But I can not see what in these files tells me what the return code of
> a function is. Is that cotained in the output?

to my knowledge this is the trick: you have to guess there is no other
way. You can inspire yourself from the old dev-ezx reversed engineered
version for a780.
-- 
 _
(�=  Marc de Courville = [EMAIL PROTECTED] = http://www.courville.org
//)  
v_/_ {Free,Net}BSD, Linux: You can also get less bang for more bucks