linux-kernel - Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <cda58cb80610271308v137a2de8vfb8123a422270144@mail.gmail.com>
Date:	Fri, 27 Oct 2006 22:08:47 +0200
From:	"Franck Bui-Huu" <vagabon.xyz@...il.com>
To:	"Miguel Ojeda" <maxextreme@...il.com>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support

On 10/26/06, Miguel Ojeda <maxextreme@...il.com> wrote:
> No way. Each controller would have different wirings, pins, in-outs,
> specifications (...) You will need to code an almost whole new fbdev
> driver (althought maybe it will be so similar to cfag12864b so you
> only need to make few little changes, but that is unsure).
>

that's what I was trying to point out. I was wondering if you could
make your driver a little more generic so another lcd could use your
driver as is.

> Well, you were right about mmaping, but you weren't about
> "info->fix.smem_start". smem_start expects a physical address. RAM
> addresses can't be mmapped as usual

Sorry I don't understand your last sentence. Can you explain please ?

-- 
               Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/