mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1-mm1
Date: Tue, 10 Oct 2006 09:57:11 +0000	[thread overview]
Message-ID: <653402b90610100257t53f62cf5y75875ed7e7cb479c@mail.gmail.com> (raw)
In-Reply-To: <20061010011052.f22a55da.akpm@osdl.org>

On 10/10/06, Andrew Morton <akpm@osdl.org> wrote:
> On Tue, 10 Oct 2006 07:31:23 +0000
> "Miguel Ojeda" <maxextreme@gmail.com> wrote:
>
> > On 10/10/06, Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > +# drivers-add-lcd-support.patch: Pavel says use fbcon
> > > +drivers-add-lcd-support.patch
> > > +drivers-add-lcd-support-update.patch
> > >
> >
> > Has the # a special meaning?
>
> It's a comment separator ;)
>

Ouch. Right.

>
> > I'm going to work on offering the fbcon feature as Pavel requested.
>
> Thanks.  It does sound like making the thing an fbdev is the right way to go.
>

Yep, such way will let us to run a xgl server through some ascii video
lib and display it on the 128x64 LCD fb device ;)

> > suggested 2 ways.
> >
> > Pavel's idea: Change the driver so the cfag12864b module will be just
> > a framebuffer device, removing access through /dev/cfag12864b.
> >
> > My idea: Code a new module called "fbcfag12864b", which will depend on
> > cfag12864b and will be the framebuffer device. This way we have both
> > devices, and they doesn't affect each other as they are different
> > things. So the ks0108 and cfag12864b can stay without any changes.
> > Also, if we finally decide we don't want the raw cfag12864b module, it
> > is easy to remove it from the cfag12864b and the fbcafg12864b will
> > continue working.
> >
> > Is there anyone who can decide which idea is better? If not, I will
> > code it my way. Also, if the Pavel's idea will be the chosen one, it
> > will be easier to put the fbcfag12864b code into the cfag12864b rather
> > than the opposite.
>
> I'd have thought that once the device is accessible as an fbdev, there's so
> much other software and kernel infrastructure to support that, there's
> little point in offering an alternative way of presenting the device to
> userspace.
>

Allright, I will code it as the fbcfag12864b module, and when it will
be working fine, I will remove the raw device of the cfag12864b and if
the code of fbcfag12864b results really small/trivial, I will put it
in the cfag12864b module. Then I will send you the "update patch 2".

Give me a couple of days or so :)

Thanks you,
     Miguel Ojeda

  reply	other threads:[~2006-10-10  9:57 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  7:09 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  7:20 ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10  7:45   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  8:03     ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 13:14       ` RSS accounting (was: Re: 2.6.19-rc1-mm1) Peter Zijlstra
2006-10-10 16:13         ` Arjan van de Ven
2006-10-10 23:54           ` Eric W. Biederman
2006-10-11  8:47             ` Arjan van de Ven
2006-10-11 12:07               ` Eric W. Biederman
2006-10-11 13:55                 ` Arjan van de Ven
2006-10-11 17:15                   ` Chen, Kenneth W
2006-10-11 22:36                     ` Benjamin LaHaise
2006-10-10  7:31 ` 2.6.19-rc1-mm1 Miguel Ojeda
2006-10-10  8:10   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  9:57     ` Miguel Ojeda [this message]
2006-10-10 18:25       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 12:19 ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-10 12:26   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 16:21   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 13:10 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 14:04   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11  5:35     ` 2.6.19-rc1-mm1 Neil Brown
2006-10-11 10:48       ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 11:23         ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11 13:08           ` _cpu_down deadlock [was Re: 2.6.19-rc1-mm1] Neil Brown
2006-10-11 13:32             ` Rusty Russell
2006-10-11 16:39             ` Andrew Morton
2006-10-11 23:46               ` Neil Brown
2006-10-12  6:51                 ` Arjan van de Ven
2006-10-12  7:53                   ` SPAM: " Neil Brown
2006-10-12  8:04                     ` Andrew Morton
2006-10-13  4:49                       ` Neil Brown
2006-10-10 15:47 ` BUG in filp_close() (was: Re: 2.6.19-rc1-mm1) Dave Kleikamp
2006-10-10 22:07   ` Dave Kleikamp
2006-10-10 22:14     ` Vadim Lobanov
2006-10-10 22:38     ` Vadim Lobanov
2006-10-10 16:09 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 19:04   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 21:44     ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 21:52       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-20 20:44         ` 2.6.19-rc1-mm1 Thomas Gleixner
2006-10-10 17:15 ` BUG() in copy_fdtable() with 64K pages (2.6.19-rc1-mm1) Olof Johansson
2006-10-10 19:34   ` Andrew Morton
2006-10-10 20:20   ` Linas Vepstas
2006-10-10 20:31     ` Vadim Lobanov
2006-10-10 23:05       ` Linas Vepstas
2006-10-10 18:09 ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 19:25   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 19:41     ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:10     ` 2.6.19-rc1-mm1 Paul Mackerras
2006-10-10 23:16       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:37       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 22:17 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  6:56   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11  3:13 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  4:01   ` 2.6.19-rc1-mm1 Andrew Morton
     [not found]     ` <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
2006-10-11 16:56       ` 2.6.19-rc1-mm1 (ext4 problem ?) Andrew Morton
2006-10-11 17:08         ` Badari Pulavarty
2006-10-11 12:51   ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-11 19:54 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 21:58   ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-16 15:56     ` 2.6.19-rc1-mm1 Andy Whitcroft
2006-10-11 19:59 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 20:10   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 21:47   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-12 10:22     ` 2.6.19-rc1-mm1 Andy Whitcroft
2006-10-12 18:09     ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-12 18:52       ` 2.6.19-rc1-mm1 Vadim Lobanov
2006-10-12 19:01         ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11 21:19 ` 2.6.19-rc1-mm1 Michael Lothian
2006-10-12 12:18 ` 2.6.19-rc1-mm1 - locks when using "dd bs=1M" from card reader Helge Hafting
2006-10-12 18:29   ` Andrew Morton
2006-10-13 13:11     ` Helge Hafting
2006-10-13 16:29       ` Andrew Morton
2006-10-13 18:10         ` [linux-usb-devel] " Alan Stern
2006-10-18  9:31           ` Helge Hafting
2006-10-18 16:26             ` Alan Stern
2006-10-19 12:25               ` Helge Hafting
2006-10-19 18:40                 ` Alan Stern
2006-10-19 18:57                   ` Christopher "Monty" Montgomery
2006-10-20 11:44                   ` Helge Hafting
2006-10-20 15:55                     ` Alan Stern
2006-10-23  9:12                       ` Helge Hafting
2006-10-23 14:13                         ` Alan Stern
2006-10-23 20:36                       ` Christopher "Monty" Montgomery
2006-10-24 10:16                         ` Helge Hafting
2006-10-24 14:09                           ` Alan Stern
2006-10-12 18:37 ` 2.6.19-rc1-mm1 Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=653402b90610100257t53f62cf5y75875ed7e7cb479c@mail.gmail.com \
    --to=maxextreme@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®