Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1528177 > unrolled thread

[RFC PATCH 0/3] staging: remove fbdev drivers

Started byTomi Valkeinen <tomi.valkeinen@ti.com>
First post2016-11-23 09:10 +0100
Last post2016-11-23 11:10 +0100
Articles 9 — 5 participants

Back to article view | Back to linux.kernel

Contents

  [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-11-23 09:10 +0100
    Re: [RFC PATCH 0/3] staging: remove fbdev drivers Daniel Vetter <daniel@ffwll.ch> - 2016-11-23 09:20 +0100
      Re: [RFC PATCH 0/3] staging: remove fbdev drivers Geert Uytterhoeven <geert@linux-m68k.org> - 2016-11-23 09:30 +0100
        Re: [RFC PATCH 0/3] staging: remove fbdev drivers Daniel Vetter <daniel@ffwll.ch> - 2016-11-23 10:10 +0100
      Re: [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-11-23 09:30 +0100
    Re: [RFC PATCH 0/3] staging: remove fbdev drivers Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-11-23 10:00 +0100
      Re: [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-11-23 10:20 +0100
        Re: [RFC PATCH 0/3] staging: remove fbdev drivers Thomas Petazzoni <thomas.petazzoni@free-electrons.com> - 2016-11-23 11:10 +0100
        Re: [RFC PATCH 0/3] staging: remove fbdev drivers Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2016-11-23 11:10 +0100

#1528177 — [RFC PATCH 0/3] staging: remove fbdev drivers

FromTomi Valkeinen <tomi.valkeinen@ti.com>
Date2016-11-23 09:10 +0100
Subject[RFC PATCH 0/3] staging: remove fbdev drivers
Message-ID<sGAMV-2jc-3@gated-at.bofh.it>
Hi,

Since the fbdev framework is in maintenance mode and all new display drivers
should be made with the DRM framework, remove the fbdev drivers from staging.

Note: the patches are created with git format-patch -D, so they can't be
applied. Only for review.

 Tomi

Tomi Valkeinen (3):
  staging: remove xgifb
  staging: remove sm750fb
  staging: remove fbtft

 MAINTAINERS                              |   19 -
 drivers/staging/Kconfig                  |    6 -
 drivers/staging/Makefile                 |    3 -
 drivers/staging/fbtft/Kconfig            |  210 --
 drivers/staging/fbtft/Makefile           |   40 -
 drivers/staging/fbtft/README             |   32 -
 drivers/staging/fbtft/fb_agm1264k-fl.c   |  456 ---
 drivers/staging/fbtft/fb_bd663474.c      |  184 -
 drivers/staging/fbtft/fb_hx8340bn.c      |  234 --
 drivers/staging/fbtft/fb_hx8347d.c       |  169 -
 drivers/staging/fbtft/fb_hx8353d.c       |  157 -
 drivers/staging/fbtft/fb_hx8357d.c       |  210 --
 drivers/staging/fbtft/fb_hx8357d.h       |   70 -
 drivers/staging/fbtft/fb_ili9163.c       |  273 --
 drivers/staging/fbtft/fb_ili9320.c       |  278 --
 drivers/staging/fbtft/fb_ili9325.c       |  277 --
 drivers/staging/fbtft/fb_ili9340.c       |  149 -
 drivers/staging/fbtft/fb_ili9341.c       |  166 -
 drivers/staging/fbtft/fb_ili9481.c       |  112 -
 drivers/staging/fbtft/fb_ili9486.c       |  112 -
 drivers/staging/fbtft/fb_pcd8544.c       |  176 -
 drivers/staging/fbtft/fb_ra8875.c        |  318 --
 drivers/staging/fbtft/fb_s6d02a1.c       |  166 -
 drivers/staging/fbtft/fb_s6d1121.c       |  194 --
 drivers/staging/fbtft/fb_ssd1289.c       |  191 --
 drivers/staging/fbtft/fb_ssd1305.c       |  216 --
 drivers/staging/fbtft/fb_ssd1306.c       |  217 --
 drivers/staging/fbtft/fb_ssd1325.c       |  205 --
 drivers/staging/fbtft/fb_ssd1331.c       |  196 --
 drivers/staging/fbtft/fb_ssd1351.c       |  238 --
 drivers/staging/fbtft/fb_st7735r.c       |  190 -
 drivers/staging/fbtft/fb_st7789v.c       |  265 --
 drivers/staging/fbtft/fb_tinylcd.c       |  112 -
 drivers/staging/fbtft/fb_tls8204.c       |  169 -
 drivers/staging/fbtft/fb_uc1611.c        |  340 --
 drivers/staging/fbtft/fb_uc1701.c        |  179 -
 drivers/staging/fbtft/fb_upd161704.c     |  197 --
 drivers/staging/fbtft/fb_watterott.c     |  302 --
 drivers/staging/fbtft/fbtft-bus.c        |  252 --
 drivers/staging/fbtft/fbtft-core.c       | 1467 --------
 drivers/staging/fbtft/fbtft-io.c         |  238 --
 drivers/staging/fbtft/fbtft-sysfs.c      |  219 --
 drivers/staging/fbtft/fbtft.h            |  421 ---
 drivers/staging/fbtft/fbtft_device.c     | 1597 ---------
 drivers/staging/fbtft/flexfb.c           |  619 ----
 drivers/staging/fbtft/internal.h         |   25 -
 drivers/staging/sm750fb/Kconfig          |   14 -
 drivers/staging/sm750fb/Makefile         |    4 -
 drivers/staging/sm750fb/TODO             |   16 -
 drivers/staging/sm750fb/ddk750.h         |   24 -
 drivers/staging/sm750fb/ddk750_chip.c    |  403 ---
 drivers/staging/sm750fb/ddk750_chip.h    |   79 -
 drivers/staging/sm750fb/ddk750_display.c |  186 -
 drivers/staging/sm750fb/ddk750_display.h |  102 -
 drivers/staging/sm750fb/ddk750_dvi.c     |   60 -
 drivers/staging/sm750fb/ddk750_dvi.h     |   59 -
 drivers/staging/sm750fb/ddk750_help.c    |   17 -
 drivers/staging/sm750fb/ddk750_help.h    |   21 -
 drivers/staging/sm750fb/ddk750_hwi2c.c   |  254 --
 drivers/staging/sm750fb/ddk750_hwi2c.h   |   11 -
 drivers/staging/sm750fb/ddk750_mode.c    |  220 --
 drivers/staging/sm750fb/ddk750_mode.h    |   41 -
 drivers/staging/sm750fb/ddk750_power.c   |  165 -
 drivers/staging/sm750fb/ddk750_power.h   |   50 -
 drivers/staging/sm750fb/ddk750_reg.h     | 1458 --------
 drivers/staging/sm750fb/ddk750_sii164.c  |  410 ---
 drivers/staging/sm750fb/ddk750_sii164.h  |  174 -
 drivers/staging/sm750fb/ddk750_swi2c.c   |  516 ---
 drivers/staging/sm750fb/ddk750_swi2c.h   |   71 -
 drivers/staging/sm750fb/readme           |   38 -
 drivers/staging/sm750fb/sm750.c          | 1248 -------
 drivers/staging/sm750fb/sm750.h          |  202 --
 drivers/staging/sm750fb/sm750_accel.c    |  388 ---
 drivers/staging/sm750fb/sm750_accel.h    |  225 --
 drivers/staging/sm750fb/sm750_cursor.c   |  183 -
 drivers/staging/sm750fb/sm750_cursor.h   |   17 -
 drivers/staging/sm750fb/sm750_hw.c       |  557 ---
 drivers/staging/xgifb/Kconfig            |   11 -
 drivers/staging/xgifb/Makefile           |    4 -
 drivers/staging/xgifb/TODO               |   13 -
 drivers/staging/xgifb/XGI_main.h         |  377 --
 drivers/staging/xgifb/XGI_main_26.c      | 2100 ------------
 drivers/staging/xgifb/XGIfb.h            |  108 -
 drivers/staging/xgifb/vb_def.h           |  256 --
 drivers/staging/xgifb/vb_init.c          | 1363 --------
 drivers/staging/xgifb/vb_init.h          |    6 -
 drivers/staging/xgifb/vb_setmode.c       | 5529 ------------------------------
 drivers/staging/xgifb/vb_setmode.h       |   23 -
 drivers/staging/xgifb/vb_struct.h        |  164 -
 drivers/staging/xgifb/vb_table.h         | 2511 --------------
 drivers/staging/xgifb/vb_util.h          |   45 -
 drivers/staging/xgifb/vgatypes.h         |   50 -
 92 files changed, 31639 deletions(-)
 delete mode 100644 drivers/staging/fbtft/Kconfig
 delete mode 100644 drivers/staging/fbtft/Makefile
 delete mode 100644 drivers/staging/fbtft/README
 delete mode 100644 drivers/staging/fbtft/fb_agm1264k-fl.c
 delete mode 100644 drivers/staging/fbtft/fb_bd663474.c
 delete mode 100644 drivers/staging/fbtft/fb_hx8340bn.c
 delete mode 100644 drivers/staging/fbtft/fb_hx8347d.c
 delete mode 100644 drivers/staging/fbtft/fb_hx8353d.c
 delete mode 100644 drivers/staging/fbtft/fb_hx8357d.c
 delete mode 100644 drivers/staging/fbtft/fb_hx8357d.h
 delete mode 100644 drivers/staging/fbtft/fb_ili9163.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9320.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9325.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9340.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9341.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9481.c
 delete mode 100644 drivers/staging/fbtft/fb_ili9486.c
 delete mode 100644 drivers/staging/fbtft/fb_pcd8544.c
 delete mode 100644 drivers/staging/fbtft/fb_ra8875.c
 delete mode 100644 drivers/staging/fbtft/fb_s6d02a1.c
 delete mode 100644 drivers/staging/fbtft/fb_s6d1121.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1289.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1305.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1306.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1325.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1331.c
 delete mode 100644 drivers/staging/fbtft/fb_ssd1351.c
 delete mode 100644 drivers/staging/fbtft/fb_st7735r.c
 delete mode 100644 drivers/staging/fbtft/fb_st7789v.c
 delete mode 100644 drivers/staging/fbtft/fb_tinylcd.c
 delete mode 100644 drivers/staging/fbtft/fb_tls8204.c
 delete mode 100644 drivers/staging/fbtft/fb_uc1611.c
 delete mode 100644 drivers/staging/fbtft/fb_uc1701.c
 delete mode 100644 drivers/staging/fbtft/fb_upd161704.c
 delete mode 100644 drivers/staging/fbtft/fb_watterott.c
 delete mode 100644 drivers/staging/fbtft/fbtft-bus.c
 delete mode 100644 drivers/staging/fbtft/fbtft-core.c
 delete mode 100644 drivers/staging/fbtft/fbtft-io.c
 delete mode 100644 drivers/staging/fbtft/fbtft-sysfs.c
 delete mode 100644 drivers/staging/fbtft/fbtft.h
 delete mode 100644 drivers/staging/fbtft/fbtft_device.c
 delete mode 100644 drivers/staging/fbtft/flexfb.c
 delete mode 100644 drivers/staging/fbtft/internal.h
 delete mode 100644 drivers/staging/sm750fb/Kconfig
 delete mode 100644 drivers/staging/sm750fb/Makefile
 delete mode 100644 drivers/staging/sm750fb/TODO
 delete mode 100644 drivers/staging/sm750fb/ddk750.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_chip.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_chip.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_display.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_display.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_dvi.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_dvi.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_help.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_help.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_hwi2c.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_hwi2c.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_mode.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_mode.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_power.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_power.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_reg.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_sii164.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_sii164.h
 delete mode 100644 drivers/staging/sm750fb/ddk750_swi2c.c
 delete mode 100644 drivers/staging/sm750fb/ddk750_swi2c.h
 delete mode 100644 drivers/staging/sm750fb/readme
 delete mode 100644 drivers/staging/sm750fb/sm750.c
 delete mode 100644 drivers/staging/sm750fb/sm750.h
 delete mode 100644 drivers/staging/sm750fb/sm750_accel.c
 delete mode 100644 drivers/staging/sm750fb/sm750_accel.h
 delete mode 100644 drivers/staging/sm750fb/sm750_cursor.c
 delete mode 100644 drivers/staging/sm750fb/sm750_cursor.h
 delete mode 100644 drivers/staging/sm750fb/sm750_hw.c
 delete mode 100644 drivers/staging/xgifb/Kconfig
 delete mode 100644 drivers/staging/xgifb/Makefile
 delete mode 100644 drivers/staging/xgifb/TODO
 delete mode 100644 drivers/staging/xgifb/XGI_main.h
 delete mode 100644 drivers/staging/xgifb/XGI_main_26.c
 delete mode 100644 drivers/staging/xgifb/XGIfb.h
 delete mode 100644 drivers/staging/xgifb/vb_def.h
 delete mode 100644 drivers/staging/xgifb/vb_init.c
 delete mode 100644 drivers/staging/xgifb/vb_init.h
 delete mode 100644 drivers/staging/xgifb/vb_setmode.c
 delete mode 100644 drivers/staging/xgifb/vb_setmode.h
 delete mode 100644 drivers/staging/xgifb/vb_struct.h
 delete mode 100644 drivers/staging/xgifb/vb_table.h
 delete mode 100644 drivers/staging/xgifb/vb_util.h
 delete mode 100644 drivers/staging/xgifb/vgatypes.h

-- 
2.7.4

[toc] | [next] | [standalone]

#1528182

FromDaniel Vetter <daniel@ffwll.ch>
Date2016-11-23 09:20 +0100
Message-ID<sGAWC-2ox-11@gated-at.bofh.it>
In reply to#1528177
On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
> Hi,
> 
> Since the fbdev framework is in maintenance mode and all new display drivers
> should be made with the DRM framework, remove the fbdev drivers from staging.
> 
> Note: the patches are created with git format-patch -D, so they can't be
> applied. Only for review.

+1 from my side. Now that we have the simple pipe helpers in drm-kms, and
a few drivers starting to use them, there's really no reasons left anymore
to have fbdev drivers.

And if anyone wants to use the code as hw documentation, git will keep it
forever.
-Daniel
> 
>  Tomi
> 
> Tomi Valkeinen (3):
>   staging: remove xgifb
>   staging: remove sm750fb
>   staging: remove fbtft
> 
>  MAINTAINERS                              |   19 -
>  drivers/staging/Kconfig                  |    6 -
>  drivers/staging/Makefile                 |    3 -
>  drivers/staging/fbtft/Kconfig            |  210 --
>  drivers/staging/fbtft/Makefile           |   40 -
>  drivers/staging/fbtft/README             |   32 -
>  drivers/staging/fbtft/fb_agm1264k-fl.c   |  456 ---
>  drivers/staging/fbtft/fb_bd663474.c      |  184 -
>  drivers/staging/fbtft/fb_hx8340bn.c      |  234 --
>  drivers/staging/fbtft/fb_hx8347d.c       |  169 -
>  drivers/staging/fbtft/fb_hx8353d.c       |  157 -
>  drivers/staging/fbtft/fb_hx8357d.c       |  210 --
>  drivers/staging/fbtft/fb_hx8357d.h       |   70 -
>  drivers/staging/fbtft/fb_ili9163.c       |  273 --
>  drivers/staging/fbtft/fb_ili9320.c       |  278 --
>  drivers/staging/fbtft/fb_ili9325.c       |  277 --
>  drivers/staging/fbtft/fb_ili9340.c       |  149 -
>  drivers/staging/fbtft/fb_ili9341.c       |  166 -
>  drivers/staging/fbtft/fb_ili9481.c       |  112 -
>  drivers/staging/fbtft/fb_ili9486.c       |  112 -
>  drivers/staging/fbtft/fb_pcd8544.c       |  176 -
>  drivers/staging/fbtft/fb_ra8875.c        |  318 --
>  drivers/staging/fbtft/fb_s6d02a1.c       |  166 -
>  drivers/staging/fbtft/fb_s6d1121.c       |  194 --
>  drivers/staging/fbtft/fb_ssd1289.c       |  191 --
>  drivers/staging/fbtft/fb_ssd1305.c       |  216 --
>  drivers/staging/fbtft/fb_ssd1306.c       |  217 --
>  drivers/staging/fbtft/fb_ssd1325.c       |  205 --
>  drivers/staging/fbtft/fb_ssd1331.c       |  196 --
>  drivers/staging/fbtft/fb_ssd1351.c       |  238 --
>  drivers/staging/fbtft/fb_st7735r.c       |  190 -
>  drivers/staging/fbtft/fb_st7789v.c       |  265 --
>  drivers/staging/fbtft/fb_tinylcd.c       |  112 -
>  drivers/staging/fbtft/fb_tls8204.c       |  169 -
>  drivers/staging/fbtft/fb_uc1611.c        |  340 --
>  drivers/staging/fbtft/fb_uc1701.c        |  179 -
>  drivers/staging/fbtft/fb_upd161704.c     |  197 --
>  drivers/staging/fbtft/fb_watterott.c     |  302 --
>  drivers/staging/fbtft/fbtft-bus.c        |  252 --
>  drivers/staging/fbtft/fbtft-core.c       | 1467 --------
>  drivers/staging/fbtft/fbtft-io.c         |  238 --
>  drivers/staging/fbtft/fbtft-sysfs.c      |  219 --
>  drivers/staging/fbtft/fbtft.h            |  421 ---
>  drivers/staging/fbtft/fbtft_device.c     | 1597 ---------
>  drivers/staging/fbtft/flexfb.c           |  619 ----
>  drivers/staging/fbtft/internal.h         |   25 -
>  drivers/staging/sm750fb/Kconfig          |   14 -
>  drivers/staging/sm750fb/Makefile         |    4 -
>  drivers/staging/sm750fb/TODO             |   16 -
>  drivers/staging/sm750fb/ddk750.h         |   24 -
>  drivers/staging/sm750fb/ddk750_chip.c    |  403 ---
>  drivers/staging/sm750fb/ddk750_chip.h    |   79 -
>  drivers/staging/sm750fb/ddk750_display.c |  186 -
>  drivers/staging/sm750fb/ddk750_display.h |  102 -
>  drivers/staging/sm750fb/ddk750_dvi.c     |   60 -
>  drivers/staging/sm750fb/ddk750_dvi.h     |   59 -
>  drivers/staging/sm750fb/ddk750_help.c    |   17 -
>  drivers/staging/sm750fb/ddk750_help.h    |   21 -
>  drivers/staging/sm750fb/ddk750_hwi2c.c   |  254 --
>  drivers/staging/sm750fb/ddk750_hwi2c.h   |   11 -
>  drivers/staging/sm750fb/ddk750_mode.c    |  220 --
>  drivers/staging/sm750fb/ddk750_mode.h    |   41 -
>  drivers/staging/sm750fb/ddk750_power.c   |  165 -
>  drivers/staging/sm750fb/ddk750_power.h   |   50 -
>  drivers/staging/sm750fb/ddk750_reg.h     | 1458 --------
>  drivers/staging/sm750fb/ddk750_sii164.c  |  410 ---
>  drivers/staging/sm750fb/ddk750_sii164.h  |  174 -
>  drivers/staging/sm750fb/ddk750_swi2c.c   |  516 ---
>  drivers/staging/sm750fb/ddk750_swi2c.h   |   71 -
>  drivers/staging/sm750fb/readme           |   38 -
>  drivers/staging/sm750fb/sm750.c          | 1248 -------
>  drivers/staging/sm750fb/sm750.h          |  202 --
>  drivers/staging/sm750fb/sm750_accel.c    |  388 ---
>  drivers/staging/sm750fb/sm750_accel.h    |  225 --
>  drivers/staging/sm750fb/sm750_cursor.c   |  183 -
>  drivers/staging/sm750fb/sm750_cursor.h   |   17 -
>  drivers/staging/sm750fb/sm750_hw.c       |  557 ---
>  drivers/staging/xgifb/Kconfig            |   11 -
>  drivers/staging/xgifb/Makefile           |    4 -
>  drivers/staging/xgifb/TODO               |   13 -
>  drivers/staging/xgifb/XGI_main.h         |  377 --
>  drivers/staging/xgifb/XGI_main_26.c      | 2100 ------------
>  drivers/staging/xgifb/XGIfb.h            |  108 -
>  drivers/staging/xgifb/vb_def.h           |  256 --
>  drivers/staging/xgifb/vb_init.c          | 1363 --------
>  drivers/staging/xgifb/vb_init.h          |    6 -
>  drivers/staging/xgifb/vb_setmode.c       | 5529 ------------------------------
>  drivers/staging/xgifb/vb_setmode.h       |   23 -
>  drivers/staging/xgifb/vb_struct.h        |  164 -
>  drivers/staging/xgifb/vb_table.h         | 2511 --------------
>  drivers/staging/xgifb/vb_util.h          |   45 -
>  drivers/staging/xgifb/vgatypes.h         |   50 -
>  92 files changed, 31639 deletions(-)
>  delete mode 100644 drivers/staging/fbtft/Kconfig
>  delete mode 100644 drivers/staging/fbtft/Makefile
>  delete mode 100644 drivers/staging/fbtft/README
>  delete mode 100644 drivers/staging/fbtft/fb_agm1264k-fl.c
>  delete mode 100644 drivers/staging/fbtft/fb_bd663474.c
>  delete mode 100644 drivers/staging/fbtft/fb_hx8340bn.c
>  delete mode 100644 drivers/staging/fbtft/fb_hx8347d.c
>  delete mode 100644 drivers/staging/fbtft/fb_hx8353d.c
>  delete mode 100644 drivers/staging/fbtft/fb_hx8357d.c
>  delete mode 100644 drivers/staging/fbtft/fb_hx8357d.h
>  delete mode 100644 drivers/staging/fbtft/fb_ili9163.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9320.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9325.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9340.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9341.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9481.c
>  delete mode 100644 drivers/staging/fbtft/fb_ili9486.c
>  delete mode 100644 drivers/staging/fbtft/fb_pcd8544.c
>  delete mode 100644 drivers/staging/fbtft/fb_ra8875.c
>  delete mode 100644 drivers/staging/fbtft/fb_s6d02a1.c
>  delete mode 100644 drivers/staging/fbtft/fb_s6d1121.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1289.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1305.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1306.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1325.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1331.c
>  delete mode 100644 drivers/staging/fbtft/fb_ssd1351.c
>  delete mode 100644 drivers/staging/fbtft/fb_st7735r.c
>  delete mode 100644 drivers/staging/fbtft/fb_st7789v.c
>  delete mode 100644 drivers/staging/fbtft/fb_tinylcd.c
>  delete mode 100644 drivers/staging/fbtft/fb_tls8204.c
>  delete mode 100644 drivers/staging/fbtft/fb_uc1611.c
>  delete mode 100644 drivers/staging/fbtft/fb_uc1701.c
>  delete mode 100644 drivers/staging/fbtft/fb_upd161704.c
>  delete mode 100644 drivers/staging/fbtft/fb_watterott.c
>  delete mode 100644 drivers/staging/fbtft/fbtft-bus.c
>  delete mode 100644 drivers/staging/fbtft/fbtft-core.c
>  delete mode 100644 drivers/staging/fbtft/fbtft-io.c
>  delete mode 100644 drivers/staging/fbtft/fbtft-sysfs.c
>  delete mode 100644 drivers/staging/fbtft/fbtft.h
>  delete mode 100644 drivers/staging/fbtft/fbtft_device.c
>  delete mode 100644 drivers/staging/fbtft/flexfb.c
>  delete mode 100644 drivers/staging/fbtft/internal.h
>  delete mode 100644 drivers/staging/sm750fb/Kconfig
>  delete mode 100644 drivers/staging/sm750fb/Makefile
>  delete mode 100644 drivers/staging/sm750fb/TODO
>  delete mode 100644 drivers/staging/sm750fb/ddk750.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_chip.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_chip.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_display.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_display.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_dvi.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_dvi.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_help.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_help.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_hwi2c.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_hwi2c.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_mode.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_mode.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_power.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_power.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_reg.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_sii164.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_sii164.h
>  delete mode 100644 drivers/staging/sm750fb/ddk750_swi2c.c
>  delete mode 100644 drivers/staging/sm750fb/ddk750_swi2c.h
>  delete mode 100644 drivers/staging/sm750fb/readme
>  delete mode 100644 drivers/staging/sm750fb/sm750.c
>  delete mode 100644 drivers/staging/sm750fb/sm750.h
>  delete mode 100644 drivers/staging/sm750fb/sm750_accel.c
>  delete mode 100644 drivers/staging/sm750fb/sm750_accel.h
>  delete mode 100644 drivers/staging/sm750fb/sm750_cursor.c
>  delete mode 100644 drivers/staging/sm750fb/sm750_cursor.h
>  delete mode 100644 drivers/staging/sm750fb/sm750_hw.c
>  delete mode 100644 drivers/staging/xgifb/Kconfig
>  delete mode 100644 drivers/staging/xgifb/Makefile
>  delete mode 100644 drivers/staging/xgifb/TODO
>  delete mode 100644 drivers/staging/xgifb/XGI_main.h
>  delete mode 100644 drivers/staging/xgifb/XGI_main_26.c
>  delete mode 100644 drivers/staging/xgifb/XGIfb.h
>  delete mode 100644 drivers/staging/xgifb/vb_def.h
>  delete mode 100644 drivers/staging/xgifb/vb_init.c
>  delete mode 100644 drivers/staging/xgifb/vb_init.h
>  delete mode 100644 drivers/staging/xgifb/vb_setmode.c
>  delete mode 100644 drivers/staging/xgifb/vb_setmode.h
>  delete mode 100644 drivers/staging/xgifb/vb_struct.h
>  delete mode 100644 drivers/staging/xgifb/vb_table.h
>  delete mode 100644 drivers/staging/xgifb/vb_util.h
>  delete mode 100644 drivers/staging/xgifb/vgatypes.h
> 
> -- 
> 2.7.4
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

[toc] | [prev] | [next] | [standalone]

#1528184

FromGeert Uytterhoeven <geert@linux-m68k.org>
Date2016-11-23 09:30 +0100
Message-ID<sGB6i-2rD-9@gated-at.bofh.it>
In reply to#1528182
Hi Daniel,

On Wed, Nov 23, 2016 at 9:19 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
>> Since the fbdev framework is in maintenance mode and all new display drivers
>> should be made with the DRM framework, remove the fbdev drivers from staging.
>>
>> Note: the patches are created with git format-patch -D, so they can't be
>> applied. Only for review.
>
> +1 from my side. Now that we have the simple pipe helpers in drm-kms, and
> a few drivers starting to use them, there's really no reasons left anymore
> to have fbdev drivers.

I haven't been following this that closely, so can you please point me to a
sample DRM driver using this simple pipe helper?

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

[toc] | [prev] | [next] | [standalone]

#1528229

FromDaniel Vetter <daniel@ffwll.ch>
Date2016-11-23 10:10 +0100
Message-ID<sGBJ0-2TX-49@gated-at.bofh.it>
In reply to#1528184
On Wed, Nov 23, 2016 at 9:25 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Hi Daniel,
>
> On Wed, Nov 23, 2016 at 9:19 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
>>> Since the fbdev framework is in maintenance mode and all new display drivers
>>> should be made with the DRM framework, remove the fbdev drivers from staging.
>>>
>>> Note: the patches are created with git format-patch -D, so they can't be
>>> applied. Only for review.
>>
>> +1 from my side. Now that we have the simple pipe helpers in drm-kms, and
>> a few drivers starting to use them, there's really no reasons left anymore
>> to have fbdev drivers.
>
> I haven't been following this that closely, so can you please point me to a
> sample DRM driver using this simple pipe helper?

Bummer, they still haven't landed. But afaik there's at least 4 of
them floating around in various places ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

[toc] | [prev] | [next] | [standalone]

#1528187

FromTomi Valkeinen <tomi.valkeinen@ti.com>
Date2016-11-23 09:30 +0100
Message-ID<sGB6i-2rD-15@gated-at.bofh.it>
In reply to#1528182

[Multipart message — attachments visible in raw view] — view raw

On 23/11/16 10:19, Daniel Vetter wrote:
> On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
>> Hi,
>>
>> Since the fbdev framework is in maintenance mode and all new display drivers
>> should be made with the DRM framework, remove the fbdev drivers from staging.
>>
>> Note: the patches are created with git format-patch -D, so they can't be
>> applied. Only for review.
> 
> +1 from my side. Now that we have the simple pipe helpers in drm-kms, and
> a few drivers starting to use them, there's really no reasons left anymore
> to have fbdev drivers.

Well, I think there's the MMU problem. If I recall right, someone said
DRM doesn't compile/work without MMU.

 Tomi

[toc] | [prev] | [next] | [standalone]

#1528210

FromGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Date2016-11-23 10:00 +0100
Message-ID<sGBzk-2Bt-23@gated-at.bofh.it>
In reply to#1528177
On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
> Hi,
> 
> Since the fbdev framework is in maintenance mode and all new display drivers
> should be made with the DRM framework, remove the fbdev drivers from staging.
> 
> Note: the patches are created with git format-patch -D, so they can't be
> applied. Only for review.

I only want to remove these drivers if we have the same functionality in
mainline for their hardware.  If not, that's a bit rude to those who
actually use them today, don't you think?

thanks,

greg k-h

[toc] | [prev] | [next] | [standalone]

#1528235

FromTomi Valkeinen <tomi.valkeinen@ti.com>
Date2016-11-23 10:20 +0100
Message-ID<sGBSG-2X2-9@gated-at.bofh.it>
In reply to#1528210

[Multipart message — attachments visible in raw view] — view raw

On 23/11/16 10:52, Greg Kroah-Hartman wrote:
> On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
>> Hi,
>>
>> Since the fbdev framework is in maintenance mode and all new display drivers
>> should be made with the DRM framework, remove the fbdev drivers from staging.
>>
>> Note: the patches are created with git format-patch -D, so they can't be
>> applied. Only for review.
> 
> I only want to remove these drivers if we have the same functionality in
> mainline for their hardware.  If not, that's a bit rude to those who
> actually use them today, don't you think?

What does it mean for a driver to be in staging? I thought it's
basically the same as the driver being out-of-tree, with the difference
that the code is in a central git repository for easier co-operation.

If that's what staging means, then I would reject the staging fbdev
drivers the same way as I'd reject new fbdev drivers sent as patches to
the list.

Or do you mean that we should keep the drivers in staging until there's
a matching DRM driver, but drop any plans to move the drivers from
staging to drivers/video/? If so, I'm fine with that. This is an RFC,
mostly to raise some discussion and push people to actually write those
DRM drivers =).

 Tomi

[toc] | [prev] | [next] | [standalone]

#1528274

FromThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date2016-11-23 11:10 +0100
Message-ID<sGCF4-3u2-33@gated-at.bofh.it>
In reply to#1528235
Hello,

On Wed, 23 Nov 2016 11:12:32 +0200, Tomi Valkeinen wrote:

> > I only want to remove these drivers if we have the same functionality in
> > mainline for their hardware.  If not, that's a bit rude to those who
> > actually use them today, don't you think?  
> 
> What does it mean for a driver to be in staging? I thought it's
> basically the same as the driver being out-of-tree, with the difference
> that the code is in a central git repository for easier co-operation.
> 
> If that's what staging means, then I would reject the staging fbdev
> drivers the same way as I'd reject new fbdev drivers sent as patches to
> the list.
> 
> Or do you mean that we should keep the drivers in staging until there's
> a matching DRM driver, but drop any plans to move the drivers from
> staging to drivers/video/? If so, I'm fine with that. This is an RFC,
> mostly to raise some discussion and push people to actually write those
> DRM drivers =).

The very reason why I submitted those drivers for staging is because
lots and lots of people were using out of tree kernel modules for these
drivers, which was really a pain.

If you now remove those drivers from staging, then those folks will be
back in the situation they originally were, using annoying out of tree
modules.

I'm all for removing fbtft drivers progressively as a matching
DRM-based driver is available for the same hardware. However, if there
is no DRM-based support for a given piece of hardware supported by
fbtft, I'd prefer if we kept the fbtft driver for this hardware.

Of course, at some point, we'll have a bunch of left-over fbtft drivers
that nobody will have converted, and we'll have to take the decision to
remove them all. But to me, the DRM-based solution for those displays
is still very young, so it makes sense to leave a bit of time for
people to convert the drivers over to the new DRM-based solution.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[toc] | [prev] | [next] | [standalone]

#1528277

FromGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Date2016-11-23 11:10 +0100
Message-ID<sGCF4-3u2-53@gated-at.bofh.it>
In reply to#1528235
On Wed, Nov 23, 2016 at 11:12:32AM +0200, Tomi Valkeinen wrote:
> On 23/11/16 10:52, Greg Kroah-Hartman wrote:
> > On Wed, Nov 23, 2016 at 10:03:10AM +0200, Tomi Valkeinen wrote:
> >> Hi,
> >>
> >> Since the fbdev framework is in maintenance mode and all new display drivers
> >> should be made with the DRM framework, remove the fbdev drivers from staging.
> >>
> >> Note: the patches are created with git format-patch -D, so they can't be
> >> applied. Only for review.
> > 
> > I only want to remove these drivers if we have the same functionality in
> > mainline for their hardware.  If not, that's a bit rude to those who
> > actually use them today, don't you think?
> 
> What does it mean for a driver to be in staging? I thought it's
> basically the same as the driver being out-of-tree, with the difference
> that the code is in a central git repository for easier co-operation.

Yes, but it also allows people to use their hardware, for drivers that
are not "quite ready".

> If that's what staging means, then I would reject the staging fbdev
> drivers the same way as I'd reject new fbdev drivers sent as patches to
> the list.

Rejecting valid drivers for hardware that people have today is not a
nice thing.  If you want to just move them into staging so that people
can get their hardware working while people port to the new apis, I will
be glad to take them.

> Or do you mean that we should keep the drivers in staging until there's
> a matching DRM driver, but drop any plans to move the drivers from
> staging to drivers/video/? If so, I'm fine with that. This is an RFC,
> mostly to raise some discussion and push people to actually write those
> DRM drivers =).

I do not want to move these to drivers/video/ and they should just stay
where they are until a matching DRM driver is present in the tree.

thanks,

greg k-h

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web