Thank You for your continued support and contributions!
The Ecos diff from last-rhepl is on the CD that came with every Rio Karma. Subsequent firmware releases didn't include any new modifications to Ecos itself. I believe that the licensing conditions allow anyone with that CD to repost the diff (but check first!); I don't have a copy to hand myself any more.
Bus 005 Device 004: ID 045a:5210 SONICblue, Inc. Rio Karma Music PlayerDevice Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x045a SONICblue, Inc. idProduct 0x5210 Rio Karma Music Player bcdDevice 1.01 iManufacturer 51 iProduct 72 iSerial 55 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 0 (Defined at Interface level) bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x88 EP 8 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
Dave E wrote:> Hi.>> I'm looking for information on the Rio Karma, and I gather that it> used eCos from the RHEPL days. Does anybody there at ecoscentric> recall receiving patches from the Karma development team while still> at Redhat?>> In discussions online, an ex-Karma developer stated that they> submitted their patches to eCos, but they're nowhere to be found> online and don't appear to have been distributed with the Karma> itself. There is also no mention of eCos at all in the Karma manuals> etc. These would appear to be a violations of the license by Digital> Networks North America (DNNA), who have been unresponsive to requests> for information.>> Any help or pointers in the right direction would be greatly appreciated.>Hi Dave.Unfortunately circumstances are against you. Your best chance ofacquiring the code is to politely persist with DNNA. Red Hat were underno obligation to either publish the code online or make it available -that is the responsibility of the authors - and I suspect thecontribution was lost within Red Hat after we left.You could try and contact Red Hat who were the copyright holder and whoprovided the license, but unfortunately I doubt you will get anyresponse or assistance from Red Hat in this regard as Red Hat no longerhave any interest in eCos. The current copyright holders, the FSF, willbe unable to help because this was all before their time.
can these picture of PCB be useful?
Page created in 0.377 seconds with 21 queries.