The link I gave is original source, which I afterwards changed according to my parameters - clock and processor memory map.
You right about offset 0x8, this is offset between ports in my 68 mode, I corrected, but it doesn't give any result.
Best regards,
Dmitriy Alekseev
----- Original Message -----
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
To: Dmitriy Alekseev <alexeev6@xxxxxxxxx>
Cc:
Sent: Thursday, May 24, 2012 5:22 PM
Subject: Re: struct tty_flip_buffer replacement in newer kernels
On Thu, 24 May 2012 03:38:42 -0700 (PDT)
Dmitriy Alekseev <alexeev6@xxxxxxxxx> wrote:
> Hi, Alan.
>
> Thank You very much for the answer!
> So, if I understand correctly, I took for example this: arch/arm/mach-omap1/board-voiceblue.c
> And made in my board specific file:
> static struct plat_serial8250_port exar_ports[] = {
> {
> .mapbase = (unsigned long)(0x30000300), // according to at91rm9200 CS2 memory map
> .flags = UPF_BOOT_AUTOCONF | UPF_IOREMAP, // I don't know, what kind of flags is suitable for me
That looks reasonable - UPF_IOREMAP tells the kernel to do the ioremap
for you, UPF_BOOT_AUTOCONF tries to autoconfigure the chip type
> .iotype = UPIO_MEM, // similar problem
> .regshift = 1,
And this guides the register spacing (1 = byte spaced, 2 = word spaced, 3
= dword spaced etc)
> .uartclk = 14745600, // Our chip clock frequency
UPIO_MEM is for MMIO, UPIO_PORT for port I/O
However the values don't look the same as the old driver you linked to -
that seems to be using 0x2800000 and then 8 byte spacing plus a 1843200
clock.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
