All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Mark Gross <mgross@linux.intel.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	"open list:REAL TIME CLOCK (RTC) SUBSYSTEM" 
	<linux-rtc@vger.kernel.org>,
	linux-watchdog@vger.kernel.org,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [GIT PULL] ib-drm-gpio-pdx86-rtc-wdt-v5.12-1
Date: Wed, 27 Jan 2021 00:19:17 +0100	[thread overview]
Message-ID: <CAMeQTsZMK9E4=qB-Kxnt9i4RGDFRkVMAgyYSck_tmk7C7yTH2A@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcEq4thOub+k5rDR61KZX4jCZj2zJr2OqsdedmpSB64KA@mail.gmail.com>

On Tue, Jan 26, 2021 at 9:53 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, Jan 26, 2021 at 8:33 PM Hans de Goede <hdegoede@redhat.com> wrote:
> > On 1/26/21 6:14 PM, Andy Shevchenko wrote:
> > > On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
> > > <patrik.r.jakobsson@gmail.com> wrote:
> > >> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
> > >> <andy.shevchenko@gmail.com> wrote:
> > >>> On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
> > >>> <patrik.r.jakobsson@gmail.com> wrote:
> > >>>> On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
> > >>>> <andriy.shevchenko@linux.intel.com> wrote:
> > >>>>>
> > >>>>> Hi guys,
> > >>>>>
> > >>>>> This is first part of Intel MID outdated platforms removal. It's collected into
> > >>>>> immutable branch with a given tag, please pull to yours subsystems.
> > >>>>
> > >>>> Hi Andy,
> > >>>> Do you plan on eventually removing X86_INTEL_MID completely? If so,
> > >>>> then I should probably start looking at removing the corresponding
> > >>>> parts in GMA500.
> > >>>
> > >>> Nope. It is related to only Medfield / Clovertrail platforms.
> > >>>
> > >>> There are other (MID) platforms that may / might utilize this driver
> > >>> in the future.
> > >>
> > >> Right, there's still Oaktrail / Moorestown with hardware in the wild.
> > >
> > > Actually Moorestown had to be removed a few years ago (kernel won't
> > > boot on them anyway from that date when Alan removed support under
> > > arch/x86 for it).

Ok. I lump Moorestown and Oaktrail together since they have the same
Z6xx series CPU/GPU (GMA600). I still have a working Oaktrail device
so that support should stay in gma500.

> > >
> > > I'm talking about Merrifield and Moorefield that can utilize it and
> > > also some other platforms that are not SFI based (Cedar something...
> > > IIRC).
> >
> > Yes at least there are some 64 bit capable SoCs with GMA500 which were
> > used in NAS like devices. These NAS-es actually have a VGA output
> > (and maybe also DVI?) which is attached to the GMA500.

Yes these should be Cedarview/Cedartrail. Some of them are 64-bit and
some are 32-bit. I think it came down to if bios enabled it or not.
Cedarview comes with VGA, DVI and eDP/DP. Quite a few Cedarview
devices exist in the wild.

>
> Since you are talking about 64-bit, definitely they are *not*
> Moorestown, Medfield, Clovertrail since the mentioned never were
> 64-bit. But it would be nice to see the CPU model number to be sure.
>
> > I know people are running Fedora on these, so we should at least keep
> > these supported.
>
> Is it possible to gather the CPU model number from them? (Or at least
> the exact device/box name)

Yes, it would be interesting to know more about Clovertrail. gma500
only supports up to the Cedarview GPUs but Clovertrail might also use
a Cedarview GPU.

-Patrik

WARNING: multiple messages have this Message-ID (diff)
From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:REAL TIME CLOCK \(RTC\) SUBSYSTEM"
	<linux-rtc@vger.kernel.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Mark Gross <mgross@linux.intel.com>,
	linux-watchdog@vger.kernel.org,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [GIT PULL] ib-drm-gpio-pdx86-rtc-wdt-v5.12-1
Date: Wed, 27 Jan 2021 00:19:17 +0100	[thread overview]
Message-ID: <CAMeQTsZMK9E4=qB-Kxnt9i4RGDFRkVMAgyYSck_tmk7C7yTH2A@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcEq4thOub+k5rDR61KZX4jCZj2zJr2OqsdedmpSB64KA@mail.gmail.com>

On Tue, Jan 26, 2021 at 9:53 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, Jan 26, 2021 at 8:33 PM Hans de Goede <hdegoede@redhat.com> wrote:
> > On 1/26/21 6:14 PM, Andy Shevchenko wrote:
> > > On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
> > > <patrik.r.jakobsson@gmail.com> wrote:
> > >> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
> > >> <andy.shevchenko@gmail.com> wrote:
> > >>> On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
> > >>> <patrik.r.jakobsson@gmail.com> wrote:
> > >>>> On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
> > >>>> <andriy.shevchenko@linux.intel.com> wrote:
> > >>>>>
> > >>>>> Hi guys,
> > >>>>>
> > >>>>> This is first part of Intel MID outdated platforms removal. It's collected into
> > >>>>> immutable branch with a given tag, please pull to yours subsystems.
> > >>>>
> > >>>> Hi Andy,
> > >>>> Do you plan on eventually removing X86_INTEL_MID completely? If so,
> > >>>> then I should probably start looking at removing the corresponding
> > >>>> parts in GMA500.
> > >>>
> > >>> Nope. It is related to only Medfield / Clovertrail platforms.
> > >>>
> > >>> There are other (MID) platforms that may / might utilize this driver
> > >>> in the future.
> > >>
> > >> Right, there's still Oaktrail / Moorestown with hardware in the wild.
> > >
> > > Actually Moorestown had to be removed a few years ago (kernel won't
> > > boot on them anyway from that date when Alan removed support under
> > > arch/x86 for it).

Ok. I lump Moorestown and Oaktrail together since they have the same
Z6xx series CPU/GPU (GMA600). I still have a working Oaktrail device
so that support should stay in gma500.

> > >
> > > I'm talking about Merrifield and Moorefield that can utilize it and
> > > also some other platforms that are not SFI based (Cedar something...
> > > IIRC).
> >
> > Yes at least there are some 64 bit capable SoCs with GMA500 which were
> > used in NAS like devices. These NAS-es actually have a VGA output
> > (and maybe also DVI?) which is attached to the GMA500.

Yes these should be Cedarview/Cedartrail. Some of them are 64-bit and
some are 32-bit. I think it came down to if bios enabled it or not.
Cedarview comes with VGA, DVI and eDP/DP. Quite a few Cedarview
devices exist in the wild.

>
> Since you are talking about 64-bit, definitely they are *not*
> Moorestown, Medfield, Clovertrail since the mentioned never were
> 64-bit. But it would be nice to see the CPU model number to be sure.
>
> > I know people are running Fedora on these, so we should at least keep
> > these supported.
>
> Is it possible to gather the CPU model number from them? (Or at least
> the exact device/box name)

Yes, it would be interesting to know more about Clovertrail. gma500
only supports up to the Cedarview GPUs but Clovertrail might also use
a Cedarview GPU.

-Patrik
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-01-27  4:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 12:38 [GIT PULL] ib-drm-gpio-pdx86-rtc-wdt-v5.12-1 Andy Shevchenko
2021-01-26 12:38 ` Andy Shevchenko
2021-01-26 14:18 ` Hans de Goede
2021-01-26 14:18   ` Hans de Goede
2021-01-26 14:26   ` Andy Shevchenko
2021-01-26 14:26     ` Andy Shevchenko
2021-02-03  9:54   ` Andy Shevchenko
2021-02-03  9:54     ` Andy Shevchenko
2021-02-03 10:35     ` Hans de Goede
2021-02-03 10:35       ` Hans de Goede
2021-02-03 11:08       ` Andy Shevchenko
2021-02-03 11:08         ` Andy Shevchenko
2021-01-26 15:22 ` Patrik Jakobsson
2021-01-26 15:22   ` Patrik Jakobsson
2021-01-26 15:51   ` Andy Shevchenko
2021-01-26 15:51     ` Andy Shevchenko
2021-01-26 16:55     ` Patrik Jakobsson
2021-01-26 16:55       ` Patrik Jakobsson
2021-01-26 17:14       ` Andy Shevchenko
2021-01-26 17:14         ` Andy Shevchenko
2021-01-26 18:33         ` Hans de Goede
2021-01-26 18:33           ` Hans de Goede
2021-01-26 20:54           ` Andy Shevchenko
2021-01-26 20:54             ` Andy Shevchenko
2021-01-26 23:19             ` Patrik Jakobsson [this message]
2021-01-26 23:19               ` Patrik Jakobsson
2021-01-27 19:59             ` Hans de Goede
2021-01-27 19:59               ` Hans de Goede
2021-02-03 11:59   ` Andy Shevchenko
2021-02-03 11:59     ` Andy Shevchenko
2021-02-04 10:19     ` Patrik Jakobsson
2021-02-04 10:19       ` Patrik Jakobsson
2021-02-04 10:36       ` Daniel Vetter
2021-02-04 10:36         ` Daniel Vetter
2021-02-04 10:50         ` Hans de Goede
2021-02-04 10:50           ` Hans de Goede
2021-02-04 10:57           ` Alexandre Belloni
2021-02-04 10:57             ` Alexandre Belloni
2021-02-04 14:27             ` Andy Shevchenko
2021-02-04 14:27               ` Andy Shevchenko
2021-02-03  9:57 ` Andy Shevchenko
2021-02-03  9:57   ` Andy Shevchenko

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='CAMeQTsZMK9E4=qB-Kxnt9i4RGDFRkVMAgyYSck_tmk7C7yTH2A@mail.gmail.com' \
    --to=patrik.r.jakobsson@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=wim@linux-watchdog.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 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.