From: robin <robin@protonic.nl>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
linux-fbdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 14/14] auxdisplay: constify fb ops
Date: Mon, 02 Dec 2019 08:08:08 +0000 [thread overview]
Message-ID: <db5f3f940317323543fe8b5adbbefff6@protonic.nl> (raw)
In-Reply-To: <CANiq72mEseWduUkJ069E8m8XKuyctsxOsTEZAfGm9d81WzpGEQ@mail.gmail.com>
On 2019-11-29 21:59, Miguel Ojeda wrote:
> On Fri, Nov 29, 2019 at 9:30 PM Daniel Vetter <daniel@ffwll.ch> wrote:
>>
>> Well we do have very small lcd display drivers in drm, and before that
>> in
>> fbdev. And you have a fbdev framebuffer driver in there, which looks a
>> bit
>> misplaced ...
>>
>> Afaiui you also have some even tinier lcd drivers where you don't
>> address
>> pixels, but just directly upload text, and those obviously don't fit
>> into
>> drm/fbdev world. But anything where you can address pixels very much
>> does.
>> -Daniel
>
> The first driver in the category used fb.h. At the time (~13 years
> ago) it was decided that the drivers should go into a different
> category/folder instead and then the other were added.
>
> In any case, I am removing the original ones since I cannot test them
> anymore and there are likely no user. The only other fb user could be
> relocated if Robin agrees.
The ht16k33 driver registers a framebuffer, backlight and input device.
Not sure if it's OK to let a driver under fbdev register all of those,
but relocating it is fine by me.
Robin
WARNING: multiple messages have this Message-ID (diff)
From: robin <robin@protonic.nl>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
linux-fbdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 14/14] auxdisplay: constify fb ops
Date: Mon, 02 Dec 2019 09:08:08 +0100 [thread overview]
Message-ID: <db5f3f940317323543fe8b5adbbefff6@protonic.nl> (raw)
In-Reply-To: <CANiq72mEseWduUkJ069E8m8XKuyctsxOsTEZAfGm9d81WzpGEQ@mail.gmail.com>
On 2019-11-29 21:59, Miguel Ojeda wrote:
> On Fri, Nov 29, 2019 at 9:30 PM Daniel Vetter <daniel@ffwll.ch> wrote:
>>
>> Well we do have very small lcd display drivers in drm, and before that
>> in
>> fbdev. And you have a fbdev framebuffer driver in there, which looks a
>> bit
>> misplaced ...
>>
>> Afaiui you also have some even tinier lcd drivers where you don't
>> address
>> pixels, but just directly upload text, and those obviously don't fit
>> into
>> drm/fbdev world. But anything where you can address pixels very much
>> does.
>> -Daniel
>
> The first driver in the category used fb.h. At the time (~13 years
> ago) it was decided that the drivers should go into a different
> category/folder instead and then the other were added.
>
> In any case, I am removing the original ones since I cannot test them
> anymore and there are likely no user. The only other fb user could be
> relocated if Robin agrees.
The ht16k33 driver registers a framebuffer, backlight and input device.
Not sure if it's OK to let a driver under fbdev register all of those,
but relocating it is fine by me.
Robin
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: robin <robin@protonic.nl>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
linux-fbdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 14/14] auxdisplay: constify fb ops
Date: Mon, 02 Dec 2019 09:08:08 +0100 [thread overview]
Message-ID: <db5f3f940317323543fe8b5adbbefff6@protonic.nl> (raw)
Message-ID: <20191202080808.VnWQybr2sfP4x1vnXdZCUMxG_lYxUOwBUwmg1QZOAsA@z> (raw)
In-Reply-To: <CANiq72mEseWduUkJ069E8m8XKuyctsxOsTEZAfGm9d81WzpGEQ@mail.gmail.com>
On 2019-11-29 21:59, Miguel Ojeda wrote:
> On Fri, Nov 29, 2019 at 9:30 PM Daniel Vetter <daniel@ffwll.ch> wrote:
>>
>> Well we do have very small lcd display drivers in drm, and before that
>> in
>> fbdev. And you have a fbdev framebuffer driver in there, which looks a
>> bit
>> misplaced ...
>>
>> Afaiui you also have some even tinier lcd drivers where you don't
>> address
>> pixels, but just directly upload text, and those obviously don't fit
>> into
>> drm/fbdev world. But anything where you can address pixels very much
>> does.
>> -Daniel
>
> The first driver in the category used fb.h. At the time (~13 years
> ago) it was decided that the drivers should go into a different
> category/folder instead and then the other were added.
>
> In any case, I am removing the original ones since I cannot test them
> anymore and there are likely no user. The only other fb user could be
> relocated if Robin agrees.
The ht16k33 driver registers a framebuffer, backlight and input device.
Not sure if it's OK to let a driver under fbdev register all of those,
but relocating it is fine by me.
Robin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-02 8:08 UTC|newest]
Thread overview: 125+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 10:29 [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 01/14] video: fb_defio: preserve user fb_ops Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 14:12 ` [Intel-gfx] " Noralf Trønnes
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 15:22 ` Daniel Vetter
2019-11-29 15:22 ` [Intel-gfx] " Daniel Vetter
2019-11-29 15:22 ` Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 02/14] drm/fb-helper: don't preserve fb_ops across deferred IO use Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 14:12 ` [Intel-gfx] " Noralf Trønnes
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 10:29 ` [PATCH v2 03/14] video: smscufx: don't restore fb_mmap after deferred IO cleanup Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 04/14] video: udlfb: " Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 05/14] video: fbdev: vesafb: modify the static fb_ops directly Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 06/14] video: fbmem: use const pointer for fb_ops Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 15:25 ` [Intel-gfx] " Daniel Vetter
2019-11-29 15:25 ` Daniel Vetter
2019-11-29 15:25 ` Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 07/14] video: omapfb: " Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-12-03 9:16 ` Jani Nikula
2019-12-03 9:16 ` [Intel-gfx] " Jani Nikula
2019-12-03 9:16 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 08/14] video: fbdev: make fbops member of struct fb_info a const pointer Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-30 1:41 ` kbuild test robot
2019-11-30 1:41 ` kbuild test robot
2019-11-30 1:41 ` [Intel-gfx] " kbuild test robot
2019-11-30 1:41 ` kbuild test robot
2019-11-30 1:41 ` kbuild test robot
2019-11-29 10:29 ` [PATCH v2 09/14] drm: constify fb ops across all drivers Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 10/14] video: " Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:35 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 11/14] HID: picoLCD: constify fb ops Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-12-02 8:40 ` Bruno Prémont
2019-12-02 8:40 ` [Intel-gfx] " Bruno Prémont
2019-12-02 8:40 ` Bruno Prémont
2019-12-02 8:40 ` Bruno Prémont
2019-12-05 9:38 ` Jani Nikula
2019-12-05 9:38 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:38 ` Jani Nikula
2019-12-05 9:38 ` Jani Nikula
2019-12-08 0:07 ` Jiri Kosina
2019-12-08 0:07 ` [Intel-gfx] " Jiri Kosina
2019-12-08 0:07 ` Jiri Kosina
2019-12-08 0:07 ` Jiri Kosina
2019-11-29 10:29 ` [PATCH v2 12/14] media: constify fb ops across all drivers Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:35 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:35 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 13/14] samples: vfio-mdev: constify fb ops Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 14/14] auxdisplay: " Jani Nikula
2019-11-29 10:29 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` Jani Nikula
2019-11-29 15:24 ` Daniel Vetter
2019-11-29 15:24 ` [Intel-gfx] " Daniel Vetter
2019-11-29 15:24 ` Daniel Vetter
2019-11-29 20:16 ` Miguel Ojeda
2019-11-29 20:16 ` [Intel-gfx] " Miguel Ojeda
2019-11-29 20:16 ` Miguel Ojeda
2019-11-29 20:30 ` Daniel Vetter
2019-11-29 20:30 ` [Intel-gfx] " Daniel Vetter
2019-11-29 20:30 ` Daniel Vetter
2019-11-29 20:59 ` Miguel Ojeda
2019-11-29 20:59 ` [Intel-gfx] " Miguel Ojeda
2019-11-29 20:59 ` Miguel Ojeda
2019-12-02 8:08 ` robin [this message]
2019-12-02 8:08 ` [Intel-gfx] " robin
2019-12-02 8:08 ` robin
2019-12-02 7:37 ` robin
2019-12-02 7:37 ` [Intel-gfx] " robin
2019-12-02 7:37 ` robin
2019-11-29 15:40 ` [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Daniel Vetter
2019-11-29 15:40 ` [Intel-gfx] " Daniel Vetter
2019-11-29 15:40 ` Daniel Vetter
2019-11-29 15:40 ` Daniel Vetter
2019-11-29 18:28 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-11-29 18:28 ` [Intel-gfx] " Patchwork
2019-11-30 16:30 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-11-30 16:30 ` [Intel-gfx] " Patchwork
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=db5f3f940317323543fe8b5adbbefff6@protonic.nl \
--to=robin@protonic.nl \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.