which driver for uartlite with 2.6.17?
David H. Lynch Jr.
dhlii at dlasys.net
Mon Oct 16 07:55:00 EST 2006
David Bolcsfoldi wrote:
> Hi :-)
>
> Good question. Well I was unaware of the fact that there were other
> uartlite drivers so you should take mine off that list. Peter's driver
> is slated for inclusion in the mainline and I am currently in the
> process of adding a few things to it.
>
> For 2.6.17 support you should probably just remove the IRQF_DISABLED
> flag and change IRQF_SAMPLE_RANDOM to SA_SAMPLE_RANDOM in the
> request_irq call and it should work. I am unaware of any other
> important differences between the two releases affecting this driver.
>
> Cheers,
> David
>
> On 10/13/06, Robert Corley <rcorley at aegis-inc.net> wrote:
>
>> All,
>>
>> Based on what was posted recently, it appears that there is more than one uartlite driver
>> floating about.
>>
>> Can someone please inform me of which driver works for which kernel?
>>
>> Here is what I see
>>
>> D. Lynch 2.6.15 polled, (Pico E12 board specific?)
>>
My driver supports polled and/or interrupt driven use - if you want
polled you set the IRQ to -1.
It should not be Pico E12 specific - I just have never tested it on
anything but the Pico E12 and E14 boards.
I do not think I have posted a patch that ONLY includes the
UartLite. At the moment it seems like it would just confuse things.
Peter and I uses fairly different Platform device initiallization.
Mine is based on the 8250 code which makes it much easier to impliment
early boot text support.
You can actually diff my driver against the 8250 driver and mostly
will find it is a subset.
My driver also has boot-bash support.
supports regshift values other than 2.
I recently patched my driver to use the major and minor nodes Peter
obtained through lanana.org as well as use his ttyUl0 naming.
I am not sure which version of the kernel the patch supports, but I
have been running my driver from 2.6.13-2.6.18.
But aside of patch issues, all of the drivers below should work
across many versions.
Yoshio Kashiwagi -Nissin Systems - Late January 2006.
Also provided a UartLite driver that was a drop in replacement for
the version I posted in January.
Yoshio's version uses DCR. His should also provide early boot text
support.
I am not sure if he posted his version but he provided me with a
copy with a GPL license so I can
post it or email it if someone wanted.
>> P. Korsgaard 2.6.18 interrupt driven, official lanana.org nodes
>>
Is only interrupt driven, only supports a regshift of 2.
Does not work for me, but aparently does for some others.
Does not have early boot text support - Davd Bolcsfoldi has provided
patches for that - though it would also be trivial to
use my driver and replace my uartlite.c with Peter's and get early
boot text support - aside from initialization issues - which appear to
be ignorable,
early boot text and the driver are very independent.
David Bolcsfoldi appears to have a few other quality related patches
to Peter's drivers which I have not had a chance to try.
>> D. Bolcsfoldi 2.6.18 interrupt driven
>>
David's also has early boot text support.
David also provided early boot text support as a patch to Peter's
driver.
>> patch locations:
>> D. Lynch http://ozlabs.org/pipermail/linuxppc-embedded/2006-January/021592.html
>> P. Korsgaard http://lkml.org/lkml/2006/9/13/71
>> D. Bolcsfoldi http://ozlabs.org/pipermail/linuxppc-embedded/2006-October/024697.html
>>
>> Comments?
>>
Yes, I think including anything in the Kernel at the moment is
premature. While I wish Peter would have started from something that
already existed.
He did do the work to register the major and minor numbers and run
his through linux-serial - though I think his submission was premature.
I know my driver has a few failure cases - none of which matter in
my environment. I also know it has not been tested on other uartlite
implimentations.
The same is true of all the other UartLite drivers listed.
Peter's and mine diverge in design almost as much as you can diverge
while still following the Linux serial driver model.
I deliberately patterned mine after the 8250 - there are pro and con
arguments for that, but atleast you know.
I am very familiar with serial hardware - I have written serial code
for the past 25 years. I am less familiar with Linux
Serial drivers. I deliberately patterened mine on an existing driver
I knew to be well supported, robust, and tolerant of
disparate and flakey hardware - partly because of my lack of depth
of Linux Serial Driver knowledge and partly because
I knew that anything that worked well for 8250's would likely work
well with other uarts.
I do not know what Peter's is based on.
I have tried to reconcile my patches with Peter's driver - basically
implimenting the functionality I have Peter is missing.
But Peter's driver does not work on my boards. I have spent a great
deal of time trying to fix that, and come to the unhappy realization
it will probably take a great deal more to solve that - much more
than it took to write my own driver in the first place.
David Bilosfoldi has posted a patch to Peter's driver that looks
like it impliments Early Boot Text support. There are minor differences
between
What David did and what I did, but on inspection he seems to have
made all the necescary patches.
Right now if one of the posted drivers does not work on your
hardware or configuration, then you are going to have to pick a driver
and try to fix it.
Peter appears to be fairly willing to provide assistance with his
driver. I am equally willing to provide help with mine.
Aparently Peter's is likely to get accepted. At least that will
provide a baseline for the rest of us to post fixes.
I am not having the problems compiling Peter's you are. That is
something you may have to take up with Peter.
But until I can get Peter's to work on my hardware, I am not posting
untested patches.
And as I have something that works for me, and as Peter's driver
seriously diverges from mine, I have a strong disincentive to put time
into it
when I have something that works.
>> And, lastly, I need a driver for 2.6.17. Can someone point me in the right direction?
>> I have tried Peter's driver but it fails to compile, showing this:
>>
>> CC drivers/serial/serial_core.o
>> CC drivers/serial/uartlite.o
>> drivers/serial/uartlite.c: In function `ulite_startup':
>> drivers/serial/uartlite.c:199: error: `IRQF_DISABLED' undeclared (first use in this function)
>> drivers/serial/uartlite.c:199: error: (Each undeclared identifier is reported only once
>> drivers/serial/uartlite.c:199: error: for each function it appears in.)
>> drivers/serial/uartlite.c:199: error: `IRQF_SAMPLE_RANDOM' undeclared (first use in this function)
>> make[2]: *** [drivers/serial/uartlite.o] Error 1
>> make[1]: *** [drivers/serial] Error 2
>> make: *** [drivers] Error 2
>>
I have been able to successfully compile Peter's driver with 2.6.18.
>>
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded at ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii at dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20061015/98118361/attachment.htm
More information about the Linuxppc-embedded
mailing list