On 27/07/2023 00:44, Rob Clark wrote:
On Wed, Jul 26, 2023 at 2:38 PM Dmitry Baryshkov
wrote:
On 27/07/2023 00:37, Rob Clark wrote:
On Thu, Jul 6, 2023 at 8:45 PM Dmitry Baryshkov
wrote:
On 07/07/2023 00:10, Rob Clark wrote:
From: Rob Clark
/* Helper for formating the chip_id in the
On Wed, Jul 26, 2023 at 2:38 PM Dmitry Baryshkov
wrote:
>
> On 27/07/2023 00:37, Rob Clark wrote:
> > On Thu, Jul 6, 2023 at 8:45 PM Dmitry Baryshkov
> > wrote:
> >>
> >> On 07/07/2023 00:10, Rob Clark wrote:
> >>> From: Rob Clark
> >>>
> >>>/* Helper for formating the chip_id in the way tha
On 27/07/2023 00:37, Rob Clark wrote:
On Thu, Jul 6, 2023 at 8:45 PM Dmitry Baryshkov
wrote:
On 07/07/2023 00:10, Rob Clark wrote:
From: Rob Clark
Since the revision becomes an opaque identifier with future GPUs, move
away from treating different ranges of bits as having a given meaning.
Th
On Thu, Jul 6, 2023 at 8:45 PM Dmitry Baryshkov
wrote:
>
> On 07/07/2023 00:10, Rob Clark wrote:
> > From: Rob Clark
> >
> > Since the revision becomes an opaque identifier with future GPUs, move
> > away from treating different ranges of bits as having a given meaning.
> > This means that we nee
On Thu, Jul 13, 2023 at 03:06:36PM -0700, Rob Clark wrote:
>
> On Thu, Jul 13, 2023 at 2:39 PM Akhil P Oommen
> wrote:
> >
> > On Fri, Jul 07, 2023 at 06:45:42AM +0300, Dmitry Baryshkov wrote:
> > >
> > > On 07/07/2023 00:10, Rob Clark wrote:
> > > > From: Rob Clark
> > > >
> > > > Since the re
On Fri, 14 Jul 2023 at 01:06, Rob Clark wrote:
>
> On Thu, Jul 13, 2023 at 2:39 PM Akhil P Oommen
> wrote:
> >
> > On Fri, Jul 07, 2023 at 06:45:42AM +0300, Dmitry Baryshkov wrote:
> > >
> > > On 07/07/2023 00:10, Rob Clark wrote:
> > > > From: Rob Clark
> > > >
> > > > Since the revision becom
On Thu, Jul 13, 2023 at 2:39 PM Akhil P Oommen wrote:
>
> On Fri, Jul 07, 2023 at 06:45:42AM +0300, Dmitry Baryshkov wrote:
> >
> > On 07/07/2023 00:10, Rob Clark wrote:
> > > From: Rob Clark
> > >
> > > Since the revision becomes an opaque identifier with future GPUs, move
> > > away from treati
On Fri, Jul 07, 2023 at 06:45:42AM +0300, Dmitry Baryshkov wrote:
>
> On 07/07/2023 00:10, Rob Clark wrote:
> > From: Rob Clark
> >
> > Since the revision becomes an opaque identifier with future GPUs, move
> > away from treating different ranges of bits as having a given meaning.
> > This means
On 07/07/2023 00:10, Rob Clark wrote:
From: Rob Clark
Since the revision becomes an opaque identifier with future GPUs, move
away from treating different ranges of bits as having a given meaning.
This means that we need to explicitly list different patch revisions in
the device table.
Signed-o
