0.17.4 is out
|
View:
New views
10 Messages
—
Rating Filter:
Alert me
|
 |
0.17.4 is out
by Nicolas Boullis
::
Rate this Message:
Hi,
I just released version 0.17.4 of the em8300 driver. This version adds (partial) support for linux 2.6.31. I write "partial" because some color problems with the OSD have been reported, using this version of the driver, with VDR and linux 2.6.31. If you experience problems using any kernel older than 2.6.31, please report it. If you experience problems using any application besides VDR, please report it. If you experience any problem besides a color problem with the OSD (or subtitles), please report it. And, last but not least, if you experience this color problem with the OSD, using this version of the em8300 driver, with VDR and linux 2.6.31, I need more information about this problem. A picture showing the problem would be nice (especially if you are using vdr's default skin). I'd also like to know whether the wrong colors keep being the same with time/reloading of the em8300 module/restart of vdr/reboot. And if you have some time to spend, I'd be happy t give you things to test. Cheers, Nicolas ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Christian Gmeiner-4
::
Rate this Message:
Hi Nicolas,
I have done an update to kernel version 2.6.31.1 and used this release. And I got osd color problems in vdr :( Here are two pictures: http://picasaweb.google.com/lh/sredir?uname=christian.gmeiner&target=ALBUM&id=5387994454666074289&authkey=Gv1sRgCIOvp-q2rPmdnwE&feat=email As freehg has lot of problems, is there a way to publish you hg tree (newi2c) at an other hosting service? sf.net? Maybe this can be helpful to find the bug... i did a quick look at the diff of the two version, but I need more time to see what changed. greets, Christian 2009/10/1 Nicolas Boullis <nboullis@...>: > Hi, > > I just released version 0.17.4 of the em8300 driver. > > This version adds (partial) support for linux 2.6.31. I write "partial" > because some color problems with the OSD have been reported, using this > version of the driver, with VDR and linux 2.6.31. > > If you experience problems using any kernel older than 2.6.31, please > report it. > > If you experience problems using any application besides VDR, please > report it. > > If you experience any problem besides a color problem with the OSD (or > subtitles), please report it. > > And, last but not least, if you experience this color problem with the > OSD, using this version of the em8300 driver, with VDR and linux 2.6.31, > I need more information about this problem. A picture showing the > problem would be nice (especially if you are using vdr's default skin). > I'd also like to know whether the wrong colors keep being the same with > time/reloading of the em8300 module/restart of vdr/reboot. And if you > have some time to spend, I'd be happy t give you things to test. > > > Cheers, > > Nicolas > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Dxr3-devel mailing list > Dxr3-devel@... > https://lists.sourceforge.net/lists/listinfo/dxr3-devel > -- Christian Gmeiner, B.Sc. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Nicolas Boullis
::
Rate this Message:
Hi Christian,
On Fri, Oct 02, 2009 at 03:39:10PM +0200, Christian Gmeiner wrote: > Hi Nicolas, > > I have done an update to kernel version 2.6.31.1 and used this > release. And I got osd color problems in vdr :( > Here are two pictures: > > http://picasaweb.google.com/lh/sredir?uname=christian.gmeiner&target=ALBUM&id=5387994454666074289&authkey=Gv1sRgCIOvp-q2rPmdnwE&feat=email Thanks for the pictures. Are the wrong colors always the same? Can you try to comment out the first call to em8300_spu_setpalette in em8300_spu.c and see if it changes the colors? (If it does, a new picture would be nice, so I can compare with the tests I can do myself.) Same question if you comment out both calls to em8300_spu_setpalette. > As freehg has lot of problems, is there a way to publish you hg tree > (newi2c) at an other hosting service? sf.net? I think there's no need to, since all the changes in the newi2c tree have been merged to the main tree (which is published on sf.net). Thanks for your help, Nicolas PS: are you usig a 32- or a 64-bit kernel? ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Jan Willies
::
Rate this Message:
Hi Nicolas,
Am 02.10.2009 22:59, schrieb Nicolas Boullis: > On Fri, Oct 02, 2009 at 03:39:10PM +0200, Christian Gmeiner wrote: >> I have done an update to kernel version 2.6.31.1 and used this >> release. And I got osd color problems in vdr :( >> Here are two pictures: >> >> http://picasaweb.google.com/lh/sredir?uname=christian.gmeiner&target=ALBUM&id=5387994454666074289&authkey=Gv1sRgCIOvp-q2rPmdnwE&feat=email > > Thanks for the pictures. Are the wrong colors always the same? Yes, they are always the same on 2.6.31. > PS: are you usig a 32- or a 64-bit kernel? 32-bit here. I'm a bit afraid to screw my fs with 2.6.31 so I can't do any testing.. regards, - jan ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Bugzilla from dr.nop@gmx.net
::
Rate this Message:
Hello,
I have another kernel crash. I just wanted to give 0.17.4 a quick try, compiled the modules and copied them over to the modules dir. I didn't have the time to analyze the the environment in depth. Oct 3 20:15:30 192.168.1.14 Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006) Oct 3 20:15:30 192.168.1.14 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 Oct 3 20:15:30 192.168.1.14 Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 Oct 3 20:15:30 192.168.1.14 em8300-0: EM8300 8300 (rev 1) Oct 3 20:15:30 192.168.1.14 Oct 3 20:15:30 192.168.1.14 bus: 0, devfn: 104, irq: 11, Oct 3 20:15:30 192.168.1.14 Oct 3 20:15:30 192.168.1.14 memory: 0xf4000000. Oct 3 20:15:30 192.168.1.14 em8300-0: mapped-memory at 0xc4c00000 Oct 3 20:15:30 192.168.1.14 em8300-0: using MTRR Oct 3 20:15:30 192.168.1.14 IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs Oct 3 20:15:30 192.168.1.14 em8300-0: detected card: Hollywood+ type 2. Oct 3 20:15:30 192.168.1.14 em8300-0: Chip revision: 2 Oct 3 20:15:30 192.168.1.14 usbcore: registered new interface driver usbfs Oct 3 20:15:30 192.168.1.14 usbcore: registered new interface driver hub Oct 3 20:15:30 192.168.1.14 usbcore: registered new device driver usb Oct 3 20:15:30 192.168.1.14 uhci_hcd: USB Universal Host Controller Interface driver Oct 3 20:15:35 192.168.1.14 em8300-0: encoder chip found but no driver found within 5 seconds Oct 3 20:15:35 192.168.1.14 BUG: unable to handle kernel Oct 3 20:15:35 192.168.1.14 NULL pointer dereference Oct 3 20:15:35 192.168.1.14 at 00000030 Oct 3 20:15:35 192.168.1.14 IP: Oct 3 20:15:35 192.168.1.14 [<c49eb04f>] em8300_i2c_lock_client+0xf/0x50 [em8300] Oct 3 20:15:35 192.168.1.14 *pde = 00000000 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Oops: 0000 [#1] Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 last sysfs file: /sys/devices/LNXSYSTM:00/modalias Oct 3 20:15:35 192.168.1.14 Modules linked in: Oct 3 20:15:35 192.168.1.14 uhci_hcd(+) Oct 3 20:15:35 192.168.1.14 usbcore Oct 3 20:15:35 192.168.1.14 em8300(+) Oct 3 20:15:35 192.168.1.14 floppy Oct 3 20:15:35 192.168.1.14 evdev Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Pid: 518, comm: modprobe Not tainted (2.6.31-VDR2 #13) Oct 3 20:15:35 192.168.1.14 EIP: 0060:[<c49eb04f>] EFLAGS: 00010286 CPU: 0 Oct 3 20:15:35 192.168.1.14 EIP is at em8300_i2c_lock_client+0xf/0x50 [em8300] Oct 3 20:15:35 192.168.1.14 EAX: 00000000 EBX: c3912800 ECX: c033be67 EDX: c3912948 Oct 3 20:15:35 192.168.1.14 ESI: c3933e00 EDI: 00000032 EBP: c3aadcc0 ESP: c3aadcb8 Oct 3 20:15:35 192.168.1.14 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Oct 3 20:15:35 192.168.1.14 Process modprobe (pid: 518, ti=c3aac000 task=c3aeeac0 task.ti=c3aac000) Oct 3 20:15:35 192.168.1.14 Stack: Oct 3 20:15:35 192.168.1.14 c49f5538 Oct 3 20:15:35 192.168.1.14 c3aadccc Oct 3 20:15:35 192.168.1.14 c3aadd88 Oct 3 20:15:35 192.168.1.14 c49eb753 Oct 3 20:15:35 192.168.1.14 c49f5538 Oct 3 20:15:35 192.168.1.14 00000000 Oct 3 20:15:35 192.168.1.14 c39128e8 Oct 3 20:15:35 192.168.1.14 c033be67 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 c49f6d10 Oct 3 20:15:35 192.168.1.14 00000000 Oct 3 20:15:35 192.168.1.14 c04a169e Oct 3 20:15:35 192.168.1.14 c3aadd78 Oct 3 20:15:35 192.168.1.14 c3aeeac0 Oct 3 20:15:35 192.168.1.14 c3aa007b Oct 3 20:15:35 192.168.1.14 c012007b Oct 3 20:15:35 192.168.1.14 ffff0000 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 00000000 Oct 3 20:15:35 192.168.1.14 ffffffc5 Oct 3 20:15:35 192.168.1.14 c0121d84 Oct 3 20:15:35 192.168.1.14 00000060 Oct 3 20:15:35 192.168.1.14 00000286 Oct 3 20:15:35 192.168.1.14 c3aadd94 Oct 3 20:15:35 192.168.1.14 c3aadd44 Oct 3 20:15:35 192.168.1.14 c0276073 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 Call Trace: Oct 3 20:15:35 192.168.1.14 [<c49eb753>] ? em8300_i2c_init2+0x293/0x460 [em8300] Oct 3 20:15:35 192.168.1.14 [<c033be67>] ? _spin_unlock_irqrestore+0x37/0x60 Oct 3 20:15:35 192.168.1.14 [<c012007b>] ? copy_process+0x5cb/0x920 Oct 3 20:15:35 192.168.1.14 [<c0121d84>] ? vprintk+0x104/0x260 Oct 3 20:15:35 192.168.1.14 [<c0276073>] ? i2c_transfer+0x93/0xb0 Oct 3 20:15:35 192.168.1.14 [<c01440bb>] ? trace_hardirqs_on+0xb/0x10 Oct 3 20:15:35 192.168.1.14 [<c014673c>] ? debug_check_no_locks_freed+0x8c/0xc0 Oct 3 20:15:35 192.168.1.14 [<c01717de>] ? kfree+0x7e/0xb0 Oct 3 20:15:35 192.168.1.14 [<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130 Oct 3 20:15:35 192.168.1.14 [<c49eacf5>] ? init_em8300+0x1d5/0x370 [em8300] Oct 3 20:15:35 192.168.1.14 [<c49f4b67>] ? em8300_probe+0x2b7/0x3f0 [em8300] Oct 3 20:15:35 192.168.1.14 [<c020488e>] ? local_pci_probe+0xe/0x10 Oct 3 20:15:35 192.168.1.14 [<c02048a7>] ? pci_call_probe+0x17/0x20 Oct 3 20:15:35 192.168.1.14 [<c0204901>] ? __pci_device_probe+0x51/0x60 Oct 3 20:15:35 192.168.1.14 [<c0204936>] ? pci_device_probe+0x26/0x60 Oct 3 20:15:35 192.168.1.14 [<c024fb04>] ? really_probe+0x94/0x130 Oct 3 20:15:35 192.168.1.14 [<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130 Oct 3 20:15:35 192.168.1.14 [<c024fc6c>] ? driver_probe_device+0x1c/0x30 Oct 3 20:15:35 192.168.1.14 [<c01386fa>] ? down+0x2a/0x40 Oct 3 20:15:35 192.168.1.14 [<c024fe09>] ? __driver_attach+0x99/0xd0 Oct 3 20:15:35 192.168.1.14 [<c024eabd>] ? bus_for_each_dev+0x3d/0x60 Oct 3 20:15:35 192.168.1.14 [<c024fe59>] ? driver_attach+0x19/0x20 Oct 3 20:15:35 192.168.1.14 [<c024fd70>] ? __driver_attach+0x0/0xd0 Oct 3 20:15:35 192.168.1.14 [<c024f257>] ? bus_add_driver+0x107/0x1c0 Oct 3 20:15:35 192.168.1.14 [<c02049b0>] ? pci_device_shutdown+0x0/0x20 Oct 3 20:15:35 192.168.1.14 [<c02049b0>] ? pci_device_shutdown+0x0/0x20 Oct 3 20:15:35 192.168.1.14 [<c02502e2>] ? driver_register+0x62/0xc0 Oct 3 20:15:35 192.168.1.14 [<c0204a1b>] ? __pci_register_driver+0x4b/0xa0 Oct 3 20:15:35 192.168.1.14 [<c49fe000>] ? em8300_init+0x0/0xcf [em8300] Oct 3 20:15:35 192.168.1.14 [<c49fe08e>] ? em8300_init+0x8e/0xcf [em8300] Oct 3 20:15:35 192.168.1.14 [<c0101027>] ? _stext+0x27/0x190 Oct 3 20:15:35 192.168.1.14 [<c014e032>] ? sys_init_module+0x132/0x1e0 Oct 3 20:15:35 192.168.1.14 [<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130 Oct 3 20:15:35 192.168.1.14 [<c01f8f44>] ? trace_hardirqs_on_thunk+0xc/0x10 Oct 3 20:15:35 192.168.1.14 [<c0102d38>] ? sysenter_do_call+0x12/0x36 Oct 3 20:15:35 192.168.1.14 Code: Oct 3 20:15:35 192.168.1.14 50 Oct 3 20:15:35 192.168.1.14 08 Oct 3 20:15:35 192.168.1.14 89 Oct 3 20:15:35 192.168.1.14 e5 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 82 Oct 3 20:15:35 192.168.1.14 c0 Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 52 Oct 3 20:15:35 192.168.1.14 5c Oct 3 20:15:35 192.168.1.14 8d Oct 3 20:15:35 192.168.1.14 04 Oct 3 20:15:35 192.168.1.14 82 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 5d Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 51 Oct 3 20:15:35 192.168.1.14 04 Oct 3 20:15:35 192.168.1.14 c1 Oct 3 20:15:35 192.168.1.14 e2 Oct 3 20:15:35 192.168.1.14 08 Oct 3 20:15:35 192.168.1.14 21 Oct 3 20:15:35 192.168.1.14 d0 Oct 3 20:15:35 192.168.1.14 c3 Oct 3 20:15:35 192.168.1.14 55 Oct 3 20:15:35 192.168.1.14 89 Oct 3 20:15:35 192.168.1.14 e5 Oct 3 20:15:35 192.168.1.14 83 Oct 3 20:15:35 192.168.1.14 ec Oct 3 20:15:35 192.168.1.14 08 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 50 Oct 3 20:15:35 192.168.1.14 18 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 40 Oct 3 20:15:35 192.168.1.14 1c Oct 3 20:15:35 192.168.1.14 83 Oct 3 20:15:35 192.168.1.14 c2 Oct 3 20:15:35 192.168.1.14 60 Oct 3 20:15:35 192.168.1.14 unparseable log message: "<8b> " Oct 3 20:15:35 192.168.1.14 40 Oct 3 20:15:35 192.168.1.14 30 Oct 3 20:15:35 192.168.1.14 8b Oct 3 20:15:35 192.168.1.14 52 Oct 3 20:15:35 192.168.1.14 64 Oct 3 20:15:35 192.168.1.14 85 Oct 3 20:15:35 192.168.1.14 c0 Oct 3 20:15:35 192.168.1.14 74 Oct 3 20:15:35 192.168.1.14 0b Oct 3 20:15:35 192.168.1.14 83 Oct 3 20:15:35 192.168.1.14 38 Oct 3 20:15:35 192.168.1.14 02 Oct 3 20:15:35 192.168.1.14 74 Oct 3 20:15:35 192.168.1.14 0a Oct 3 20:15:35 192.168.1.14 ff Oct 3 20:15:35 192.168.1.14 80 Oct 3 20:15:35 192.168.1.14 18 Oct 3 20:15:35 192.168.1.14 01 Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 00 Oct 3 20:15:35 192.168.1.14 Oct 3 20:15:35 192.168.1.14 EIP: [<c49eb04f>] Oct 3 20:15:35 192.168.1.14 em8300_i2c_lock_client+0xf/0x50 [em8300] Oct 3 20:15:35 192.168.1.14 SS:ESP 0068:c3aadcb8 Oct 3 20:15:35 192.168.1.14 CR2: 0000000000000030 Oct 3 20:15:35 192.168.1.14 ---[ end trace da645eb6f5f3fb2a ]--- ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Christian Gmeiner-4
::
Rate this Message:
Hi Nicolas,
doing only this: case EM8300_IOCTL_SPU_SETPALETTE: if (copy_from_user(clu, (void *) arg, 16 * 4)) return -EFAULT; //em8300_spu_setpalette(em, clu); break; results in the same wrong picture as in previous mail. doing only this; int em8300_spu_open(struct em8300_s *em) { em->sp_ptsfifo_ptr = 0; em->sp_ptsvalid = 0; em->sp_mode = 1; //em8300_spu_setpalette(em, default_palette); write_ucregister(SP_Command, 0x2); return 0; } results in a new image: http://picasaweb.google.com/christian.gmeiner/Devel#5389194589710723970 and doing both results also in the new image. Ohh and..... 32-bit kernel. 2009/10/2 Nicolas Boullis <nboullis@...>: > Hi Christian, > > On Fri, Oct 02, 2009 at 03:39:10PM +0200, Christian Gmeiner wrote: >> Hi Nicolas, >> >> I have done an update to kernel version 2.6.31.1 and used this >> release. And I got osd color problems in vdr :( >> Here are two pictures: >> >> http://picasaweb.google.com/lh/sredir?uname=christian.gmeiner&target=ALBUM&id=5387994454666074289&authkey=Gv1sRgCIOvp-q2rPmdnwE&feat=email > > Thanks for the pictures. Are the wrong colors always the same? > Can you try to comment out the first call to em8300_spu_setpalette in > em8300_spu.c and see if it changes the colors? (If it does, a new > picture would be nice, so I can compare with the tests I can do myself.) > Same question if you comment out both calls to em8300_spu_setpalette. > > >> As freehg has lot of problems, is there a way to publish you hg tree >> (newi2c) at an other hosting service? sf.net? > > I think there's no need to, since all the changes in the newi2c tree > have been merged to the main tree (which is published on sf.net). > > > Thanks for your help, > > Nicolas > > PS: are you usig a 32- or a 64-bit kernel? > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Dxr3-devel mailing list > Dxr3-devel@... > https://lists.sourceforge.net/lists/listinfo/dxr3-devel > -- Christian Gmeiner, B.Sc. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Nicolas Boullis
::
Rate this Message:
Hi Sebastian,
On Mon, Oct 05, 2009 at 06:59:33PM +0200, Sebastian Frei wrote: > Hello, > > I have another kernel crash. I just wanted to give 0.17.4 a quick try, compiled the modules and > copied them over to the modules dir. I didn't have the time to analyze the the environment in depth. > (...) > Oct 3 20:15:35 192.168.1.14 em8300-0: encoder chip found but no driver found within 5 seconds (...) > Oct 3 20:15:35 192.168.1.14 Modules linked in: > Oct 3 20:15:35 192.168.1.14 uhci_hcd(+) > Oct 3 20:15:35 192.168.1.14 usbcore > Oct 3 20:15:35 192.168.1.14 em8300(+) > Oct 3 20:15:35 192.168.1.14 floppy > Oct 3 20:15:35 192.168.1.14 evdev Hmmm... It looks like the em8300 driver did not find the adv717x module. Did you forget to run "depmod -a"? > Oct 3 20:15:35 192.168.1.14 EIP is at em8300_i2c_lock_client+0xf/0x50 [em8300] Anyway, it's no reason for em8300_i2c_lock_client to crash! I should be able to write a patch to fix that within a few days (I know where the problem is, I have to find the best way to fix it.) Thanks Sebastian for your report, -- Nicolas ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Nicolas Boullis
::
Rate this Message:
Hi Christian,
On Mon, Oct 05, 2009 at 09:15:06PM +0200, Christian Gmeiner wrote: > Hi Nicolas, > > doing only this: > > case EM8300_IOCTL_SPU_SETPALETTE: > if (copy_from_user(clu, (void *) arg, 16 * 4)) > return -EFAULT; > //em8300_spu_setpalette(em, clu); > break; > > results in the same wrong picture as in previous mail. That's a very interesting point. It means that the EM8300_IOCTL_SPU_SETPALETTE ioctl does nothing... But I still have no idea why... Does the dxr3 plugin check the return value of this ioctl? > doing only this; > > int em8300_spu_open(struct em8300_s *em) > { > em->sp_ptsfifo_ptr = 0; > em->sp_ptsvalid = 0; > em->sp_mode = 1; > //em8300_spu_setpalette(em, default_palette); > write_ucregister(SP_Command, 0x2); > > return 0; > } > > results in a new image: > http://picasaweb.google.com/christian.gmeiner/Devel#5389194589710723970 > > and doing both results also in the new image. > > > Ohh and..... 32-bit kernel. Hmmm... Can you also check with both calls to em8300_spu_setpalette disabled, the same version of vdr and its dxr3 plugin, but a kernel < 2.6.31? And the same with only the first calls to em8300_spu_setpalette disabled? If you get the same results as with linux 2.6.31, I think that would confirm that the em8300_spu_setpalette function works fine, and that the problem is really related to the ioctl... Thanks Christian for your help, -- Nicolas ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Christian Gmeiner-4
::
Rate this Message:
2009/10/5 Nicolas Boullis <nboullis@...>:
> Hi Christian, > > On Mon, Oct 05, 2009 at 09:15:06PM +0200, Christian Gmeiner wrote: >> Hi Nicolas, >> >> doing only this: >> >> case EM8300_IOCTL_SPU_SETPALETTE: >> if (copy_from_user(clu, (void *) arg, 16 * 4)) >> return -EFAULT; >> //em8300_spu_setpalette(em, clu); >> break; >> >> results in the same wrong picture as in previous mail. > > That's a very interesting point. It means that the > EM8300_IOCTL_SPU_SETPALETTE ioctl does nothing... But I still have no > idea why... Does the dxr3 plugin check the return value of this ioctl? With commit 1b9e3804075c2dc6f70beb2e9d14ecbb6f23710c I done a minute ago it does check all ioctl syscalls. > > >> doing only this; >> >> int em8300_spu_open(struct em8300_s *em) >> { >> em->sp_ptsfifo_ptr = 0; >> em->sp_ptsvalid = 0; >> em->sp_mode = 1; >> //em8300_spu_setpalette(em, default_palette); >> write_ucregister(SP_Command, 0x2); >> >> return 0; >> } >> >> results in a new image: >> http://picasaweb.google.com/christian.gmeiner/Devel#5389194589710723970 >> >> and doing both results also in the new image. >> >> >> Ohh and..... 32-bit kernel. > > Hmmm... Can you also check with both calls to em8300_spu_setpalette > disabled, the same version of vdr and its dxr3 plugin, but a kernel < > 2.6.31? And the same with only the first calls to em8300_spu_setpalette > disabled? So here are the results with the same plugin/vdr version and kernel 2.6.29: If i disable both em8300_spu_setpalette calls I get an osd with the colors like in http://picasaweb.google.com/christian.gmeiner/Devel#5389194589710723970 If i disable the em8300_spu_setpalette call in em8300_spu_ioctl function I get a good looking OSD with different colors. This makes sense as the default plaette colors are set. If i enable all em8300_spu_setpalette calls I get a good looking OSD with correct color palette used. > > If you get the same results as with linux 2.6.31, I think that would > confirm that the em8300_spu_setpalette function works fine, and that the > problem is really related to the ioctl... I dont know if its ioctl related, as on 2.6.31 the default color palette gets not set. So there might be a problem with register writes. Hope I could help you -- Christian Gmeiner, MSc PS: Sorry for the long delay... I am very busy with vdr-plugin-dxr3 at the moment. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
|
|
Re: 0.17.4 is out
by Nicolas Boullis
::
Rate this Message:
Hi,
On Thu, Oct 15, 2009 at 11:11:36AM +0200, Christian Gmeiner wrote: > > With commit 1b9e3804075c2dc6f70beb2e9d14ecbb6f23710c I done a minute > ago it does check all ioctl syscalls. So what? Does it report any failed ioctl? (I'm afraid it does not...) > So here are the results with the same plugin/vdr version and kernel 2.6.29: > > If i disable both em8300_spu_setpalette calls I get an osd with the > colors like in > http://picasaweb.google.com/christian.gmeiner/Devel#5389194589710723970 OK. At least, this is good news: It means that if nothing tries to set the palette, then we get the same palette (I guess it is hardcoded in the firmware) with linux 2.6.29 and 2.6.31. Nothing is changing the palette behind the scene. > If i disable the em8300_spu_setpalette call in em8300_spu_ioctl > function I get a good > looking OSD with different colors. This makes sense as the default > plaette colors are set. Do you mean it is also different from the palette you had in http://picasaweb.google.com/christian.gmeiner/Devel#5389194526505276370 ? If it is, I think this is really bad news. I think it would mean that the em8300_spu_setpalette function fails to work fine with 2.6.31, always setting the palette to the same palette (and I have absolutely no idea where this palette comes from). But reading the code of the function, I don't se anything that could fail. > If i enable all em8300_spu_setpalette calls I get a good looking OSD > with correct color palette > used. At least it means that the hardware is good, and that the em8300 driver still works fine with linux 2.6.29. > I dont know if its ioctl related, as on 2.6.31 the default color > palette gets not set. It looks like you're right. > So there might be a problem with register writes. I can't imagine there is such a problem, as there are many other places where write_register: if this function did not work, I think many other things would not work. Moreover, the palette gets changed, since you have a different palette when all calls to em8300_spu_setpalette are disabled (the palette hardcoded in the firmware). > Hope I could help you Unfortunately, not that much, since I now have no idea what fails... It might be worth trying "funny" things, like replacing both pal[i] in em8300_spu_setpalette with: * pal[(i+8)%16] * (((unsigned)i)<<24) | 0xFF0000 > PS: Sorry for the long delay... I am very busy with vdr-plugin-dxr3 at > the moment. No problem. As far as I am concerned, I don't use 2.6.31, so I'm not affected by this bug... Cheers, Nicolas ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Dxr3-devel mailing list Dxr3-devel@... https://lists.sourceforge.net/lists/listinfo/dxr3-devel |
| Free embeddable forum powered by Nabble | Forum Help |
