Nabble - HW+ / DXR3 device driver for Linux

Re: vdr, em8300 0.17.4 and OSD

2009-11-24T04:13:57Z

Hi,

okay... the kernel is too new for 0.17.3. It looks like I have some
hours free to work on it today. Maybe I can
find the bug.

lg
--
Christian Gmeiner, MSc

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

From forum: dxr3-devel

Re: vdr, em8300 0.17.4 and OSD

2009-11-24T04:09:01Z

I forgot to say, then even applying the proposed em8300.patch I still
cannot compile modules, compilation hangs up with the following:

[vdr@archvdr modules]$ LANG=C make
[ ! -x ./update_em8300_version.sh ] || ./update_em8300_version.sh
em8300_version.h
make -C /lib/modules/2.6.31-ARCH/build
SUBDIRS=/home/vdr/install/em8300/em8300-0.17.3/modules modules
make[1]: Entering directory `/usr/src/linux-2.6.31-ARCH'
CC [M] /home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.o
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c:236: error:
unknown field 'detach_client' specified in initializer
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c:236: warning:
initialization from incompatible pointer type
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c: In function
'adv717x_detect':
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c:726: error:
implicit declaration of function 'i2c_attach_client'
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c: In function
'adv717x_detach_client':
/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.c:756: error:
implicit declaration of function 'i2c_detach_client'
make[2]: *** [/home/vdr/install/em8300/em8300-0.17.3/modules/adv717x.o]
Error 1
make[1]: *** [_module_/home/vdr/install/em8300/em8300-0.17.3/modules]
Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.31-ARCH'
make: *** [build] Error 2

Regards,

Yarema

> The problem is know and I suggest you to switch back to em8300-0.17.3
> and the OSD should be fixed.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

From forum: dxr3-devel

Re: vdr, em8300 0.17.4 and OSD

2009-11-23T10:02:31Z

Right, problem is known, I have read the all thread about it. I even
tried to compile 0.17.3, but compilation stops with

~/install/em8300/em8300-0.17.3/modules/Kbuild:67: /Rules.make: No such
file or directory

As far I understand, there is some disagreement with kernel (2.6.31) and
lately it was fixed in 0.17.4.

Yarema

Christian Gmeiner написав(ла):
> The problem is know and I suggest you to switch back to em8300-0.17.3
> and the OSD should be fixed.
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

From forum: dxr3-devel

Re: vdr, em8300 0.17.4 and OSD

2009-11-23T09:33:15Z

The problem is know and I suggest you to switch back to em8300-0.17.3
and the OSD should be fixed.

2009/11/23 YUP <yupadmin@...>:

> Hi,
>
> I have a problem with the current em8300 driver. Actually I'm using
> archlinux with the stock 2.6.31 kernel, em8300-0.17.4 drivers and vdr
> 1.7.0 with dxr3 plugin. I have read that the previous version, 0.17.3,
> had the same bug with OSD.
> I uploaded few of my screenshots: http://omploader.org/vMnU5aQ ,
> http://omploader.org/vMnU5bA , http://omploader.org/vMnU5bQ . I can also
> provide any additional information, logs etc. Just please let me know
> what you need.
>
> Regards,
>
> Yarema
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Dxr3-devel mailing list
> Dxr3-devel@...
> https://lists.sourceforge.net/lists/listinfo/dxr3-devel
>

--
Christian Gmeiner, MSc

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

From forum: dxr3-devel

vdr, em8300 0.17.4 and OSD

2009-11-23T07:37:44Z

Hi,

I have a problem with the current em8300 driver. Actually I'm using
archlinux with the stock 2.6.31 kernel, em8300-0.17.4 drivers and vdr
1.7.0 with dxr3 plugin. I have read that the previous version, 0.17.3,
had the same bug with OSD.
I uploaded few of my screenshots: http://omploader.org/vMnU5aQ ,
http://omploader.org/vMnU5bA , http://omploader.org/vMnU5bQ . I can also
provide any additional information, logs etc. Just please let me know
what you need.

Regards,

Yarema

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

From forum: dxr3-devel

[Pull Request]

2009-10-16T04:03:41Z

Hi Nicolas,

at the moment I try to implement stillpicture support into the
vdr-plugin-dxr3, but I run into some problems with playmodes.
And after a quick look at the driver I found out why. Many playmodes
are not supported and the ioctl does always return 0.
Hope this patch get in... and I am quite sure I will find other places
where I will write a patch for.

http://hg.assembla.com/em8300-cgmeiner

thanks
--
Christian Gmeiner, MSc

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-15T13:54:59Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-15T02:11:36Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-05T14:11:10Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-05T14:02:45Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-05T12:15:06Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-05T09:59:33Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-03T04:04:41Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-02T13:59:10Z

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

From forum: dxr3-devel

Re: 0.17.4 is out

2009-10-02T06:39:10Z

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
>

From forum: dxr3-devel

0.17.4 is out

2009-09-30T15:00:25Z

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-27T03:01:18Z

Nicolas Boullis wrote:
> Hi,
>
> On Mon, Sep 21, 2009 at 07:40:51PM +0200, Adam wrote:
>> Works with 2.6.31
>
> Thanks for your report.
> Jan and Sebastian both reported problems with 2.6.31 using vdr. What
> application do you use?
>

Hello,

I'm using mplayer

Regards,
Adam

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Fourth release-candidate for 0.17.4 -- please test!

2009-09-26T15:17:42Z

Hi,

Thanks to Sebastian Frei's report, I found a few problems that were
still in rc3.
Hence, I just packed a new release candidate for 0.17.4.
As usual you can get it from
http://dxr3.sourceforge.net/download/em8300-0.17.4-rc4.tar.gz

All comments are welcome. Please give it a try and report. (Even if you
don't use a bleeding-edge kernel, things may be broken for old kernels
as well.)

Note that I read about problems when the em8300 drivers are used with
vdr and linux 2.6.31. I won't consider this a showstopper for 0.17.4,
since :
* it apparently does not affect users of linux < 2.6.31, so there is no
regression,
* it apparently does not affect osers of other applications, even with
linux 2.6.31.

Anyway, I'm willing to fix this, and consider the fix will deserve a new
release by itself. But I have no idea where the problem lies, so any
extra information is welcome. Are the wrong colors constant or do they
change with restarts of vdr, unloading/reloading of the em8300 module,
reboot, etc? A picture would be welcome (especially using vdr's default
skin).

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

From forum: dxr3-devel

Re: Third release-candidate for 0.17.4 -- please test!

2009-09-25T00:05:08Z

Am Donnerstag, 24. September 2009 23:11:23 schrieb Nicolas Boullis:

> Hi,
>
> Sebastian Frei pointed a kernel ooops when the em8300 module fails to
> load the driver for the video encoder chip.
> Hence, I just packed a new release candidate for 0.17.4.
> As usual you can get it from
> http://dxr3.sourceforge.net/download/em8300-0.17.4-rc3.tar.gz
>
> All comments are welcome. Please give it a try and report. (Even if you
> don't use a bleeding-edge kernel, things may be broken for old kernels
> as well.)
>
>
> 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
>

Hello,

VDR works, but shows wrong OSD colours.
I tried various loading and unloading modules scenarios, and didn't get any kernel crashs.

I'll try a newer version of the dxr3 plugin to see if it solves the OSD issue.

S.

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-24T23:40:49Z

Am Donnerstag, 24. September 2009 23:08:33 schrieb Nicolas Boullis:

> Hi,
>
> On Wed, Sep 23, 2009 at 09:54:52PM +0200, Sebastian Frei wrote:
> > I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers
> > directory, where all the other modules also are. Depmod did run.
>
> Did you run it youself?
> I just tried to "make install" the modules; make reported that "DEPMOD"
> was run, but the modules.alias file and its friends were not updated.
> Because of this, the em8300 module would not find the adv717x or bt865
> modules.
> I then ran "depmod -a" myself, and then everything was fine.
> I have no idea why "make install" did not really run depmod...
>

Yes I ran "depmod -a" myself after copying the modules into the modules directory.

> > I'll try tomorrow if everything works after loading the adv717x module
> > manually.
>
Some tests, stiill with rc2:

/lib/modules/2.6.31-VDR2>modprobe em8300

dmesg:
Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4c80000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0

/lib/modules/2.6.31-VDR2>modprobe adv717x

dmesg:
adv717x.o: ADV7170 rev. 0 chip probed

/lib/modules/2.6.31-VDR2>em8300setup
Microcode uploaded to /dev/em8300-0
Current settings are:
Video Aspect Audio Spu
PAL 4:3 ANALOG OFF

dmesg:
em8300-0: Microcode version 0x29 loaded

/lib/modules/2.6.31-VDR2>rmmod adv717x em8300
Killed

dmesg:
BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4bf420a>] release_em8300+0x9a/0xd0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: em8300(-) uhci_hcd usbcore floppy evdev [last unloaded: adv717x]

Pid: 663, comm: rmmod Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4bf420a>] EFLAGS: 00010246 CPU: 0
EIP is at release_em8300+0x9a/0xd0 [em8300]
EAX: c3935600 EBX: 00000000 ECX: 00000000 EDX: 00000002
ESI: c3922800 EDI: c389b400 EBP: c3bcfedc ESP: c3bcfed4
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process rmmod (pid: 663, ti=c3bce000 task=c388aa00 task.ti=c3bce000)
Stack:
c3922800 c389b458 c3bcfef0 c4bfeb8d c389b400 c4c04e90 c4c04e90 c3bcfefc
<0> c02049aa c389b458 c3bcff0c c024fee4 c389b458 c389b48c c3bcff20 c024fff8
<0> c4c04e90 00000000 bff8f1d0 c3bcff2c c024f34d c4c04e90 c3bcff44 c0250387
Call Trace:
[<c4bfeb8d>] ? em8300_remove+0x3d/0x60 [em8300]
[<c02049aa>] ? pci_device_remove+0x3a/0x40
[<c024fee4>] ? __device_release_driver+0x84/0xd0
[<c024fff8>] ? driver_detach+0x88/0xc0
[<c024f34d>] ? bus_remove_driver+0x3d/0x60
[<c0250387>] ? driver_unregister+0x47/0x50
[<c025014f>] ? driver_remove_file+0xf/0x20
[<c0204a8a>] ? pci_unregister_driver+0x1a/0x30
[<c4bfebc2>] ? em8300_exit+0x12/0x28 [em8300]
[<c014c2f4>] ? sys_delete_module+0x164/0x170
[<c0145feb>] ? __lock_release+0x3b/0x60
[<c0102d6b>] ? sysenter_exit+0xf/0x18
[<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130
[<c01f8f44>] ? trace_hardirqs_on_thunk+0xc/0x10
[<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: 8b 80 38 01 00 00 e8 66 cc 55 fb 8b 46 5c 85 c0 75 3f 89 f0 e8 68 d5 57 fb 5b 5e 5d c3 8d 74
26 00 8b 58 1c 31 c9 ba 02 00 00 00 <ff> 53 24 8b 46 78 85 c0 0f 84 74 ff ff ff 90 8d b4 26 00 00 00
EIP: [<c4bf420a>] release_em8300+0x9a/0xd0 [em8300] SS:ESP 0068:c3bcfed4
CR2: 0000000000000024
---[ end trace 3528eaa7d6a88e3f ]---

another test, now I saw that em8300 and adv717x were blacklisted in the modprobe.conf file:

/etc/modprobe.d>modprobe em8300

/etc/modprobe.d>lsmod
Module Size Used by
adv717x 9096 0
em8300 71316 0
uhci_hcd 23832 0
usbcore 131288 1 uhci_hcd
floppy 56904 0
evdev 10884 0

/etc/modprobe.d>em8300setup
Microcode uploaded to /dev/em8300-0
Current settings are:
Video Aspect Audio Spu
PAL 4:3 ANALOG OFF

/etc/modprobe.d>rmmod adv717x

/etc/modprobe.d>lsmod
Module Size Used by
em8300 71316 0
uhci_hcd 23832 0
usbcore 131288 1 uhci_hcd
floppy 56904 0
evdev 10884 0

/etc/modprobe.d>modprobe adv717x
/etc/modprobe.d>em8300setup
Killed

dmesg:
Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4c80000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
adv717x.o: ADV7170 rev. 0 chip probed
Sigma Designs EM8300 0000:00:0d.0: PCI INT A disabled
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4f00000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
adv717x.o: ADV7170 rev. 0 chip probed
em8300-0: Microcode version 0x29 loaded
BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4c3a8ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: adv717x em8300 uhci_hcd usbcore floppy evdev [last unloaded: adv717x]

Pid: 734, comm: em8300setup Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4c3a8ca>] EFLAGS: 00010296 CPU: 0
EIP is at em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
EAX: c39d2000 EBX: 00000000 ECX: 00000005 EDX: 00000001
ESI: c3a67000 EDI: 00000005 EBP: c2c49e30 ESP: c2c49e24
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process em8300setup (pid: 734, ti=c2c48000 task=c38809e0 task.ti=c2c48000)
Stack:
00000090 00000000 c3a67000 c2c49e50 c4c3815e c2c49e50 00000286 00000286
<0> c3a90000 c3a67000 00000000 c2c49e84 c4c3a574 c0436980 c0436980 c3b0a1e0
<0> c396c0ac fffffffa 094dc008 0000666e 00000000 c2c49eb4 40084300 bfcadea8
Call Trace:
[<c4c3815e>] ? em8300_video_setup+0x3de/0x490 [em8300]
[<c4c3a574>] ? em8300_ioctl_init+0x74/0x220 [em8300]
[<c4c3a0ba>] ? em8300_control_ioctl+0x78a/0xbd0 [em8300]
[<c0144f9c>] ? __lock_acquire+0x22c/0x7f0
[<c0173800>] ? fd_install+0x40/0x50
[<c014414b>] ? trace_hardirqs_off+0xb/0x10
[<c014673c>] ? debug_check_no_locks_freed+0x8c/0xc0
[<c017173c>] ? kmem_cache_free+0x5c/0x80
[<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130
[<c4c34240>] ? em8300_io_ioctl+0x0/0x90 [em8300]
[<c4c3429d>] ? em8300_io_ioctl+0x5d/0x90 [em8300]
[<c0180918>] ? vfs_ioctl+0x48/0x70
[<c01813b4>] ? do_vfs_ioctl+0x74/0x1c0
[<c0181539>] ? sys_ioctl+0x39/0x60
[<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: ec 5d c3 89 96 9c 06 00 00 89 f0 bf 01 00 00 00 e8 dc e6 ff ff 8b 86 38 04 00 00 85 c0 74 c5 89
f6 8b 58 1c 89 f9 ba 01 00 00 00 <ff> 53 24 eb b4 90 85 d2 bf 05 00 00 00 74 93 e9 75 ff ff ff 89
EIP: [<c4c3a8ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300] SS:ESP 0068:c2c49e24
CR2: 0000000000000024
---[ end trace b423a404c69981b2 ]---

After a reboot without blacklisted modules, the em8300 and the adv717x module were loaded
automatically and VDR works but with wrong OSD colours.

S.

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Third release-candidate for 0.17.4 -- please test!

2009-09-24T14:11:23Z

Hi,

Sebastian Frei pointed a kernel ooops when the em8300 module fails to
load the driver for the video encoder chip.
Hence, I just packed a new release candidate for 0.17.4.
As usual you can get it from
http://dxr3.sourceforge.net/download/em8300-0.17.4-rc3.tar.gz

All comments are welcome. Please give it a try and report. (Even if you
don't use a bleeding-edge kernel, things may be broken for old kernels
as well.)

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-24T14:08:33Z

Hi,

On Wed, Sep 23, 2009 at 09:54:52PM +0200, Sebastian Frei wrote:
> I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers directory, where all the other
> modules also are. Depmod did run.

Did you run it youself?
I just tried to "make install" the modules; make reported that "DEPMOD"
was run, but the modules.alias file and its friends were not updated.
Because of this, the em8300 module would not find the adv717x or bt865
modules.
I then ran "depmod -a" myself, and then everything was fine.
I have no idea why "make install" did not really run depmod...

> I'll try tomorrow if everything works after loading the adv717x module manually.

Any result?

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-23T12:54:52Z

Am Dienstag, 22. September 2009 22:47:28 schrieb Nicolas Boullis:

> Hi Sebastian,
>
> On Tue, Sep 22, 2009 at 02:17:23PM +0200, Sebastian Frei wrote:
> > Hello,
> >
> > this crash occured after loading the module and starting VDR.
> >
> > Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy
> > evdev
>
> Hmmm... No adv717x or bt865 module? That's strange...
> Is it possible that the em8300 module tried to load the adv717x module
> but did not find it?
> A guess is that you did not install the modules in /lib/modules/... or
> did not run depmod.
>
> That would explain the Ooops (although it certainly has to be fixed)...
>
>
> Regards,
>

I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers directory, where all the other
modules also are. Depmod did run.
I'll try tomorrow if everything works after loading the adv717x module manually.

S.

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-22T13:47:28Z

Hi Sebastian,

On Tue, Sep 22, 2009 at 02:17:23PM +0200, Sebastian Frei wrote:
> Hello,
>
> this crash occured after loading the module and starting VDR.
>
> Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy evdev

Hmmm... No adv717x or bt865 module? That's strange...
Is it possible that the em8300 module tried to load the adv717x module
but did not find it?
A guess is that you did not install the modules in /lib/modules/... or
did not run depmod.

That would explain the Ooops (although it certainly has to be fixed)...

Regards,

--
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-22T05:17:23Z

Hello,

this crash occured after loading the module and starting VDR.

Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4c80000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4c498ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy evdev

Pid: 962, comm: vdr Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4c498ca>] EFLAGS: 00010296 CPU: 0
EIP is at em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
EAX: c3935600 EBX: 00000000 ECX: 00000005 EDX: 00000001
ESI: c39a8800 EDI: 00000005 EBP: c397fe30 ESP: c397fe24
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process vdr (pid: 962, ti=c397e000 task=c384e090 task.ti=c397e000)
Stack:
00000090 00000000 c39a8800 c397fe50 c4c4715e c397fe50 00000286 00000286
<0> c3b48000 c39a8800 00000000 c397fe84 c4c49574 0000010e c397fe98 c01435d2
<0> 00000001 c07ee7a0 09f5eea0 0000666e 00000001 c0806418 40084300 bfdc83b8
Call Trace:
[<c4c4715e>] ? em8300_video_setup+0x3de/0x490 [em8300]
[<c4c49574>] ? em8300_ioctl_init+0x74/0x220 [em8300]
[<c01435d2>] ? validate_chain+0x3d2/0x4e0
[<c4c490ba>] ? em8300_control_ioctl+0x78a/0xbd0 [em8300]
[<c01837ec>] ? dput+0xcc/0xd0
[<c0145feb>] ? __lock_release+0x3b/0x60
[<c01896d6>] ? mntput_no_expire+0x16/0x80
[<c4c43240>] ? em8300_io_ioctl+0x0/0x90 [em8300]
[<c4c4329d>] ? em8300_io_ioctl+0x5d/0x90 [em8300]
[<c0180918>] ? vfs_ioctl+0x48/0x70
[<c01813b4>] ? do_vfs_ioctl+0x74/0x1c0
[<c0181539>] ? sys_ioctl+0x39/0x60
[<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: ec 5d c3 89 96 9c 06 00 00 89 f0 bf 01 00 00 00 e8 dc e6 ff ff 8b 86 38 04 00 00 85 c0 74 c5 89
f6 8b 58 1c 89 f9 ba 01 00 00 00 <ff> 53 24 eb b4 90 85 d2 bf 05 00 00 00 74 93 e9 75 ff ff ff 89
EIP: [<c4c498ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300] SS:ESP 0068:c397fe24
CR2: 0000000000000024
---[ end trace 03568fd5c311d885 ]---

I don't have physical access to the machine until Saturday, so debugging is a bit complicated.

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-21T12:33:51Z

Hi,

On Mon, Sep 21, 2009 at 07:40:51PM +0200, Adam wrote:
>
> Works with 2.6.31

Thanks for your report.
Jan and Sebastian both reported problems with 2.6.31 using vdr. What
application do you use?

Regards,

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-21T10:40:51Z

Nicolas Boullis pisze:
> Thanks for your report.
> Anyone else wants to give it a try?
> Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
> (probably tomorrow).

Hello,

Works with 2.6.31

Thanks again

--
Regards,
Adam

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-20T13:28:39Z

Hi Sebastian,

On Sun, Sep 20, 2009 at 10:36:34AM +0200, Sebastian Frei wrote:
>
> Hello,
>
> I tried the rc2 with kernel 2.6.31 yesterday, but I got various kernel OOPSes
> and wrong OSD colours with VDR.
> This could be an issue not related to the dxr3 driver, I don't know. I'll try
> again this evening with a debug kernel.

Thanks for your report, although this certainly is bad news.
You made no change to the userspace applications you are using, did you?
It certainly looks like the problem Jan Willies described a little while
ago. But he also reported that his problem vanished when switching back
to 2.6.30, while I'm pretty confident the source code for the em8300,
adv717x and bt865 modules is excatly the same for kernels 2.6.30 and
2.6.31...
It would be nice if you could send a backtrace of your kernel OOPSes,
with the hope it is related to the color problem you have...

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-20T01:36:34Z

Am Samstag, 19. September 2009 23:12:07 schrieb Nicolas Boullis:

> Hi Jan,
>
> On Fri, Sep 18, 2009 at 08:20:35AM +0200, Jan Willies wrote:
> > Hi Nicolas,
> >
> > Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> > > All comments are welcome. Please give it a try and report. (Even if you
> > > don't use a bleeding-edge kernel, things may be broken for old kernels
> > > as well.)
> >
> > Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
> > Had to switch back to .30 because my filesystem didn't like the new
> > kernel too much.
>
> Thanks for your report.
> Anyone else wants to give it a try?
> Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
> (probably tomorrow).
>
>
> Regards,
>
> 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
>

Hello,

I tried the rc2 with kernel 2.6.31 yesterday, but I got various kernel OOPSes
and wrong OSD colours with VDR.
This could be an issue not related to the dxr3 driver, I don't know. I'll try
again this evening with a debug kernel.

S.

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-19T14:12:07Z

Hi Jan,

On Fri, Sep 18, 2009 at 08:20:35AM +0200, Jan Willies wrote:

> Hi Nicolas,
>
> Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> > All comments are welcome. Please give it a try and report. (Even if you
> > don't use a bleeding-edge kernel, things may be broken for old kernels
> > as well.)
>
> Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
> Had to switch back to .30 because my filesystem didn't like the new
> kernel too much.

Thanks for your report.
Anyone else wants to give it a try?
Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
(probably tomorrow).

Regards,

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

From forum: dxr3-devel

Re: Second release-candidate for 0.17.4 -- please test!

2009-09-17T23:20:35Z

Hi Nicolas,

Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> All comments are welcome. Please give it a try and report. (Even if you
> don't use a bleeding-edge kernel, things may be broken for old kernels
> as well.)

Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
Had to switch back to .30 because my filesystem didn't like the new
kernel too much.

thanks,

- 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

From forum: dxr3-devel

Second release-candidate for 0.17.4 -- please test!

2009-09-15T15:29:27Z

Hi,

Jan Willies discovered a problem with the first RC, that was published
yesterday.
Hence, I just packed a new release candidate for 0.17.4.
As usual you can get it from
http://dxr3.sourceforge.net/download/em8300-0.17.4-rc2.tar.gz

All comments are welcome. Please give it a try and report. (Even if you
don't use a bleeding-edge kernel, things may be broken for old kernels
as well.)

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

From forum: dxr3-devel

Re: First release-candidate for 0.17.4 -- please test!

2009-09-15T01:47:05Z

Hi Nicolas,

Am 15.09.2009 10:35, schrieb Nicolas Boullis:
> Is that using a kernel you built yourself or a kernel provided by a distro?

This is a vanilla kernel, which I've built myself.

> Anyway, this quick patch should help, and I'll try to pack up a new RC asap.

Yes, it works fine with your patch.

thanks,

- 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

From forum: dxr3-devel

Re: First release-candidate for 0.17.4 -- please test!

2009-09-15T01:35:33Z

Hi Jan and others,

Selon Jan Willies <jan@...>:

> [jan@server modules]$ LANG=C make
> [ ! -x ./update_em8300_version.sh ] || ./update_em8300_version.sh
> em8300_version.h
> make -C /lib/modules/2.6.31/build
> SUBDIRS=/usr/local/src/em8300-0.17.4-rc1/modules modules
> make[1]: Entering directory `/usr/src/linux-2.6.31'
> /usr/local/src/em8300-0.17.4-rc1/modules/Kbuild:67: /Rules.make: No such
> file or directory
> make[2]: *** No rule to make target `/Rules.make'. Stop.

Oh, thanks for reporting this.
I experienced this at home with linux 2.6.30, and thought it was related to
something strange Debian does with its kernel headers...
Is that using a kernel you built yourself or a kernel provided by a distro?

Anyway, this quick patch should help, and I'll try to pack up a new RC asap.

Cheers,

Nicolas

[em8300.patch]

diff -r e10d20ee23a6 modules/Kbuild --- a/modules/Kbuild Tue Sep 15 01:43:59 2009 +0200 +++ b/modules/Kbuild Tue Sep 15 10:31:46 2009 +0200 @@ -59,8 +59,7 @@ obj-m += bt865.o obj-m += em8300.o -# The following hack tests for old kernels (2.4 and old 2.5). -ifneq ($(TOPDIR),$(shell /bin/pwd)) +ifeq ($(shell expr $(VERSION) \* 10000 + $(PATCHLEVEL) \* 100 + $(SUBLEVEL) \< 20600),1) EXTRA_CFLAGS += -include $(TOPDIR)/include/linux/config.h

------------------------------------------------------------------------------
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

From forum: dxr3-devel

Re: First release-candidate for 0.17.4 -- please test!

2009-09-14T23:43:49Z

Hi Nicolas,

Am 15.09.2009 01:59, schrieb Nicolas Boullis:
> All comments are welcome. Please give it a try and report. (Even if you
> don't use a bleeding-edge kernel, things may be broken for old kernels
> as well.)

[jan@server modules]$ LANG=C make
[ ! -x ./update_em8300_version.sh ] || ./update_em8300_version.sh
em8300_version.h
make -C /lib/modules/2.6.31/build
SUBDIRS=/usr/local/src/em8300-0.17.4-rc1/modules modules
make[1]: Entering directory `/usr/src/linux-2.6.31'
/usr/local/src/em8300-0.17.4-rc1/modules/Kbuild:67: /Rules.make: No such
file or directory
make[2]: *** No rule to make target `/Rules.make'. Stop.

- 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

From forum: dxr3-devel