RE: Fedora 2.6.13.x kernels and hcfpci modem

Jonathan,

That's correct.

I have an up to date FC4 installation with the FC5 development kernel.

The kernel is built using the kernel-2.6.spec, with the only modification
being to set the FC4 flag instead of FC5.

The development branch requires a handful of updated RPMs including kudzu,
udev, ppp and some others that I can't tell you off hand, but they don't
appear to affect this issue as I have used these updated RPMs with the
current FC4 kernel (2.6.12-1.1447) in order to exclude them from the
problem.

The initial fact I noted was that around the 2.6.13-1.1542 development
kernel, the definition of ASYNC_CALLOUT_ACTIVE disappeared from the
linux/serial.h header file in the kernel's build tree.

A quick search on the net seemed to indicate that callout related code was
slowly being removed from the kernel... I have not had a chance to dig
deeper into the issue yet.

As I mentioned in my original post, I was just thinking out loud and realise
that I'm travelling down an unsupported path, but was curious about the
implications of the evolving kernel!

Regards,

alex

----
Alex Farkas
PhD BSc(Hons) GradCertMgmt MIEAust CPEng
magamnak at hotmail dot com
+61 8 8300 4478

>
>
>-----Original Message-----
>From: Linuxant support (Jonathan) [mailto:[email protected]]
>Sent: Friday, 16 September 2005 19:11
>To: [email protected]
>Cc: [email protected]
>Subject: Re: [hcflinux] Fedora 2.6.13.x kernels and hcfpci modem
>
>Hi,
>
>we are not aware of this problem and we will investigate. The
>'2.6.13-1.1542' kernel you are referring to is a Fedora Core 5
>development kernel?
>
>Regards,
>
>
>Jonathan
>Technical specialist / Linuxant
>www.linuxant.com
>[email protected]
>
>
>
>Alex F wrote:
> > Hi there,
> >
> > I am using the hcfpci modem drivers on Fedore Core 4 and I also run
> > custom kernels from the Fedora development branch.
> >
> > I noticed from about 2.6.13-1.1542 onwards, the ASYNC_CALLOUT_ACTIVE
> > definition had been removed from the kernel's header files and that the
> > 1.06 drivers stopped working - up to then, the 1.06 driver (with the
> > patches applied) compiled correctly.
> >
> > Actually, it is not so much that the driver would not compile but that
> > there were 4 names that could nod be resolved at load time:
> >
> > uart_register_port
> > uart_unregister_port
> > cnxthcf_cnxt_serial_remove
> > cnxthcf_cnxt_serial_add
> >
> > I realise that the "official" kernel is the only one that really needs
> > to be supported, but I am curious to know whether these later 2.6.13
> > kernels are being tracked and whether this issue is likely to be
> > resolved in the near future.
> >
> > All I have been able to gather from web blogs is that serial callout
> > related code was being purged from the 2.6.x kernel... I have not been
> > able to find anything more specific at this stage.
> >
> > I can provide debug dumps, but as I said I realise that it is impossible
> > for Linuxant to support every unofficial kernel out there so I am not
> > expecting an immediate solution!
> >
> > alex
> >
> > _______________________
> >
> > Dr Sándor Farkas, CPEng.
> > Voice: +61 (0)8 8300 4478
> > _______________________
> >
> >
> > _______________________________________________
> > hcflinux mailing list
> > [email protected]
> > https://www.linuxant.com/mailman/listinfo/hcflinux
>