search for: rev3

[+cc Konrad, xen-devel] On Wed, Oct 02, 2013 at 04:43:46PM -0400, Aaron Opfer wrote: > First time submitting the kernel dev list, so if I have demonstrated > gross incompetence in some way, please cut me some slack. :) > > I discussed with Clemens Ladisch an issue I was having that I thought > was related to the driver he authored for my soundcard, but on his > suggestion I

On 10/04/2013 06:29 PM, Bjorn Helgaas wrote: > [+cc Konrad, xen-devel] > > On Wed, Oct 02, 2013 at 04:43:46PM -0400, Aaron Opfer wrote: >> First time submitting the kernel dev list, so if I have demonstrated >> gross incompetence in some way, please cut me some slack. :) >> >> I discussed with Clemens Ladisch an issue I was having that I thought >> was

...; I'd suggest to expand nouveau_decode_mod() to take a drm_framebuffer and > return the correct values. Kind of what you do in > nouveau_framebuffer_new() near line 330. > > Thoughts? > > Best regards > Thomas > > [1] https://patchwork.freedesktop.org/series/70786/#rev3 > >> >> Thanks, >> -James >> >> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: >>> After its cleanup, struct nouveau_framebuffer is only a wrapper around >>> struct drm_framebuffer. Use the latter directly. >>> >>> Signed-off-by: Th...

...> >> return the correct values. Kind of what you do in > >> nouveau_framebuffer_new() near line 330. > >> > >> Thoughts? > >> > >> Best regards > >> Thomas > >> > >> [1] https://patchwork.freedesktop.org/series/70786/#rev3 > >> > >>> > >>> Thanks, > >>> -James > >>> > >>> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: > >>>> After its cleanup, struct nouveau_framebuffer is only a wrapper around > >>>> struct drm_framebuffe...

Hi, Thank you for your work on this card! I have quite a few boxes that run various 3wares cards with diverse firmware revs. Are there any caveats with respect to models and firmware versions in terms of how they might interact ? ---Mike At 01:25 PM 10/08/2003 -0700, Paul Saab wrote: >ps 2003/08/10 13:25:46 PDT > > FreeBSD src repository > >

...ou do in >>>>> nouveau_framebuffer_new() near line 330. >>>>> >>>>> Thoughts? >>>>> >>>>> Best regards >>>>> Thomas >>>>> >>>>> [1] https://patchwork.freedesktop.org/series/70786/#rev3 >>>>> >>>>>> >>>>>> Thanks, >>>>>> -James >>>>>> >>>>>> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: >>>>>>> After its cleanup, struct nouveau_framebuffer is only a wrapper a...

...e extracted from the framebuffer at any time. I'd suggest to expand nouveau_decode_mod() to take a drm_framebuffer and return the correct values. Kind of what you do in nouveau_framebuffer_new() near line 330. Thoughts? Best regards Thomas [1] https://patchwork.freedesktop.org/series/70786/#rev3 > > Thanks, > -James > > On 2/6/20 2:19 AM, Thomas Zimmermann wrote: >> After its cleanup, struct nouveau_framebuffer is only a wrapper around >> struct drm_framebuffer. Use the latter directly. >> >> Signed-off-by: Thomas Zimmermann <tzimmermann at suse...

...au_decode_mod() to take a drm_framebuffer and >> return the correct values. Kind of what you do in >> nouveau_framebuffer_new() near line 330. >> >> Thoughts? >> >> Best regards >> Thomas >> >> [1] https://patchwork.freedesktop.org/series/70786/#rev3 >> >>> >>> Thanks, >>> -James >>> >>> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: >>>> After its cleanup, struct nouveau_framebuffer is only a wrapper around >>>> struct drm_framebuffer. Use the latter directly. >>>...

...e correct values. Kind of what you do in >>>> nouveau_framebuffer_new() near line 330. >>>> >>>> Thoughts? >>>> >>>> Best regards >>>> Thomas >>>> >>>> [1] https://patchwork.freedesktop.org/series/70786/#rev3 >>>> >>>>> >>>>> Thanks, >>>>> -James >>>>> >>>>> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: >>>>>> After its cleanup, struct nouveau_framebuffer is only a wrapper around >>>>>&g...

...au_framebuffer_new() near line 330. > >>>>> > >>>>> Thoughts? > >>>>> > >>>>> Best regards > >>>>> Thomas > >>>>> > >>>>> [1] https://patchwork.freedesktop.org/series/70786/#rev3 > >>>>> > >>>>>> > >>>>>> Thanks, > >>>>>> -James > >>>>>> > >>>>>> On 2/6/20 2:19 AM, Thomas Zimmermann wrote: > >>>>>>> After its cleanup, struct nouv...

On Wed, Aug 07, 2013 at 08:04:07PM -0700, Sudeep Dutt wrote: > +/** > + * struct mic_device - MIC device information for each card. > + * > + * @name: Unique name for this MIC device. > + * @mmio: MMIO bar information. > + * @pdev: The PCI device structure. > + * @family: The MIC family to which this device belongs. > + * @ops: MIC HW specific operations. > + * @id: The

On Wed, Aug 07, 2013 at 08:04:07PM -0700, Sudeep Dutt wrote: > +/** > + * struct mic_device - MIC device information for each card. > + * > + * @name: Unique name for this MIC device. > + * @mmio: MMIO bar information. > + * @pdev: The PCI device structure. > + * @family: The MIC family to which this device belongs. > + * @ops: MIC HW specific operations. > + * @id: The

Note I'm adding some fields to nouveau_framebuffer in the series "drm/nouveau: Support NVIDIA format modifiers." I sent out v3 of that yesterday. It would probably still be possible to avoid them by re-extracting the relevant data from the format modifier on the fly when needed, but it is simpler and likely less error-prone with the wrapper struct. Thanks, -James On 2/6/20