On Sat, Aug 06, 2022 at 07:26:07PM +0300, Markuss Broks wrote:
> Hi Greg,
>
> On 7/28/22 18:01, Greg Kroah-Hartman wrote:
> > On Thu, Jul 28, 2022 at 05:52:04PM +0300, Markuss Broks wrote:
> > > Hi Greg,
> > >
> > > On 7/28/22 17:39, Greg Kroah-Hartman wrote:
> > > > On Thu, Jul 28, 2022 at 05:28
On Fri, Aug 5, 2022 at 6:03 AM Dave Airlie wrote:
>
> On Thu, 4 Aug 2022 at 17:44, Oded Gabbay wrote:
> >
> > On Thu, Aug 4, 2022 at 2:54 AM Dave Airlie wrote:
> > >
> > > On Thu, 4 Aug 2022 at 06:21, Oded Gabbay wrote:
> > > >
> > > > On Wed, Aug 3, 2022 at 10:04 PM Dave Airlie wrote:
> > > >
On Fri, Aug 5, 2022 at 3:22 AM Jason Gunthorpe wrote:
>
> On Thu, Aug 04, 2022 at 08:48:28PM +0300, Oded Gabbay wrote:
>
> > > The flip is true of DRM - DRM is pretty general. I bet I could
> > > implement an RDMA device under DRM - but that doesn't mean it should
> > > be done.
> > >
> > > My big
Oh, facepalm. I didn’t even think to look at the numeric value. Sorry for the
confusion.
From: Simon Ser
Sent: Saturday, August 6, 2022 3:10:53 PM
To: Hoosier, Matt
Cc: Pekka Paalanen; dri-devel@lists.freedesktop.org;
wayland-de...@lists.freedesktop.org
Subject:
On Sat, Aug 6, 2022 at 6:38 PM Markuss Broks wrote:
>
> Add early console support for generic linear framebuffer devices.
> This driver supports probing from cmdline early parameters
> or from the device-tree using information in simple-framebuffer node.
> The EFI functionality should be retained
On Saturday, August 6th, 2022 at 21:56, Hoosier, Matt
wrote:
> Any idea what’s up with some compositors adding code to infer
> DRM_FORMAT_MOD_LINEAR semantics when the buffer’s modifiers are set
> to 0?
What does that mean? A buffer only has a single modifier, and LINEAR == 0.
> Wlroots, for e
The following changes since commit ff6992735ade75aae3e35d16b17da1008d753d28:
Linux 5.19-rc7 (2022-07-17 13:30:22 -0700)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
tags/for-5.20/fbdev-1
for you to fetch changes up to 6ba592f
Hi Pekka,
Thanks. If I paraphrase, I think you’re telling me that gbm_bo_get_modifiers()
== 0 is not strong enough then.
That fits with the notes on the drm_fourcc.h declaration of the linear format
flag:
https://elixir.bootlin.com/linux/latest/source/include/uapi/drm/drm_fourcc.h#L448
Any id
On Sat, Aug 6, 2022 at 6:37 PM Markuss Broks wrote:
>
> The "node" argument is actually an offset, and it's also
> an "int", and not "unsigned long". Correct the of_setup_earlycon
> function.
Suggested-by: Greg KH?
> Signed-off-by: Markuss Broks
--
With Best Regards,
Andy Shevchenko
Pass a pointer to device-tree node in case the driver probed from
OF. This makes early console drivers able to fetch options from
device-tree node properties.
Signed-off-by: Markuss Broks
---
drivers/tty/serial/earlycon.c | 3 +++
include/linux/serial_core.h | 1 +
2 files changed, 4 insertion
The "node" argument is actually an offset, and it's also
an "int", and not "unsigned long". Correct the of_setup_earlycon
function.
Signed-off-by: Markuss Broks
---
drivers/tty/serial/earlycon.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/tty/se
Make the EFI earlycon driver be suitable for any linear framebuffers.
This should be helpful for early porting of boards with no other means of
output, like smartphones/tablets. There seems to be an issue with early_ioremap
function on ARM32, but I am unable to find the exact cause. It appears the
Add early console support for generic linear framebuffer devices.
This driver supports probing from cmdline early parameters
or from the device-tree using information in simple-framebuffer node.
The EFI functionality should be retained in whole.
The driver was disabled on ARM because of a bug in ea
Hi Greg,
On 7/28/22 18:01, Greg Kroah-Hartman wrote:
On Thu, Jul 28, 2022 at 05:52:04PM +0300, Markuss Broks wrote:
Hi Greg,
On 7/28/22 17:39, Greg Kroah-Hartman wrote:
On Thu, Jul 28, 2022 at 05:28:19PM +0300, Markuss Broks wrote:
Add early console support for generic linear framebuffer dev
On Fri, Aug 05, 2022 at 03:53:41PM -0600, Jim Cromie wrote:
> Rework/modernize docs:
>
> - use /proc/dynamic_debug/control in examples
>its *always* there (when dyndbg is config'd), even when is not.
>drop talk, its a distraction here.
>
> - alias ddcmd='echo $* > /proc/dynamic_debug/
On Fri, 5 Aug 2022 12:32:01 +
"Hoosier, Matt" wrote:
> Suppose that I want to map a GPU buffer to the CPU and do image
> analysis on it. I know all the usual cautions about this being a
> poor performance option, etc. But suppose for the moment that the
> use-case requires it.
>
> What's the
16 matches
Mail list logo
