On 7/5/23 15:13, Frank Binns wrote:
On Mon, 2023-06-26 at 10:38 -0500, Adam Ford wrote:
On Mon, Jun 26, 2023 at 8:22 AM Frank Binns wrote:
Hi Adam,
On Sat, 2023-06-17 at 07:48 -0500, Adam Ford wrote:
On Tue, Jun 13, 2023 at 10:20 AM Sarah Walker wrote:
Read the GPU ID register at probe tim
On Mon, 2023-06-26 at 10:38 -0500, Adam Ford wrote:
> On Mon, Jun 26, 2023 at 8:22 AM Frank Binns wrote:
> > Hi Adam,
> >
> > On Sat, 2023-06-17 at 07:48 -0500, Adam Ford wrote:
> > > On Tue, Jun 13, 2023 at 10:20 AM Sarah Walker
> > > wrote:
> > > > Read the GPU ID register at probe time and s
On Mon, Jun 26, 2023 at 8:22 AM Frank Binns wrote:
>
> Hi Adam,
>
> On Sat, 2023-06-17 at 07:48 -0500, Adam Ford wrote:
> > On Tue, Jun 13, 2023 at 10:20 AM Sarah Walker
> > wrote:
> > > Read the GPU ID register at probe time and select the correct
> > > features/quirks/enhancements. Use the GPU
Hi Adam,
On Sat, 2023-06-17 at 07:48 -0500, Adam Ford wrote:
> On Tue, Jun 13, 2023 at 10:20 AM Sarah Walker wrote:
> > Read the GPU ID register at probe time and select the correct
> > features/quirks/enhancements. Use the GPU ID to form the firmware
> > file name and load the firmware.
>
> I h
On Tue, Jun 13, 2023 at 10:20 AM Sarah Walker wrote:
>
> Read the GPU ID register at probe time and select the correct
> features/quirks/enhancements. Use the GPU ID to form the firmware
> file name and load the firmware.
I have a Rogue 6250 variant, but the BVNC is returning a slightly
different
Read the GPU ID register at probe time and select the correct
features/quirks/enhancements. Use the GPU ID to form the firmware
file name and load the firmware.
The features/quirks/enhancements arrays are currently hardcoded in
the driver for the supported GPUs. We are looking at moving this
infor
