I don't think anyone was ever able to get their hands on a K80 to
confirm. It's a different ID than the GK110 (0xf0) / GK110B (0xf1). I
believe it's referred to as a GK210, but not sure if that's just a
marketing thing or if it's actually different.
You can try copying the 0xf1 entry in devinit
On Sat, Dec 2, 2023 at 8:18 AM Bagas Sanjaya wrote:
>
> On Thu, Nov 30, 2023 at 11:48:24AM +0100, Gert Vanhaerents wrote:
> > Hi Kernel list,
> > I'm the IT person of a school, earlier we used multiseatcomputers for the
> > school, i have maded with a XGL implementation and it works fine but not
On Fri, Jan 12, 2024 at 11:50 AM Jani Nikula wrote:
>
> Prefer the parsed results for is_hdmi and has_audio in display info over
> calling drm_detect_hdmi_monitor() and drm_detect_monitor_audio(),
> respectively.
>
> Conveniently, this also removes the need to use edid_blob_ptr.
>
> Cc: Karol
On Mon, Dec 4, 2023 at 11:04 AM Ilia Mirkin wrote:
>
> On Sun, Dec 3, 2023 at 11:37 AM Monty Montgomery wrote:
> > 1) The nv50 DMA code clearly believed push buffers could not (or
> > should not) exceed NV50_DMA_PUSH_MAX_LENGTH, when my analysis logging
> > shows th
On Sun, Dec 3, 2023 at 11:37 AM Monty Montgomery wrote:
> 1) The nv50 DMA code clearly believed push buffers could not (or
> should not) exceed NV50_DMA_PUSH_MAX_LENGTH, when my analysis logging
> shows that they regularly exceed this maximum by an order of magnitude
> or more. Was the
On Fri, May 26, 2023 at 5:11 AM Karol Herbst wrote:
>
> 1ba6113a90a0 removed a lot of the kernel GPU channel, but method 0x128
> was important as otherwise the GPU spams us with `CACHE_ERROR` messages.
>
> We use the blit subchannel inside our vblank handling, so we should keep
> at least this
On Fri, Nov 4, 2022 at 12:56 PM Lukas Satin wrote:
>
> Hello, sorry fo the typos. Wanted to catch you before the weekend, to get
> some hints for upcoming work.
>
> I'm back at PC.
>
> Does your driver support switching to 240p in NTSC and 288p in PAL on the go
> via xrandr, for example?
>
> If
https://nouveau.freedesktop.org/KernelModuleParameters.html
Perhaps nouveau.tv_norm=NTSC-M will help get you the 60hz modes? I
haven't played with these options much at all, it has always sorta
Just Worked for me.
This should have the validation of new modes, make sure you don't run
afoul of
Hi Joe,
On Sun, May 29, 2022 at 6:58 PM Joe wrote:
>
> Hi all, I'm trying to make running hardware acceleration decoding on
> my old GeForce 210 (AKA GT-218, or NVA8 / NV-50 Tesla family).
> --
> 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218
>
On Tue, Mar 15, 2022 at 6:10 AM Martin Knoblauch wrote:
>
> On Tue, Mar 15, 2022 at 10:55 AM Martin Knoblauch wrote:
> >
> > On Mon, Mar 14, 2022 at 10:42 PM Ilia Mirkin wrote:
> > >
> > > On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch
> > > wro
On Mon, Mar 14, 2022 at 5:30 PM Martin Knoblauch wrote:
>
> On Mon, Mar 14, 2022 at 7:45 PM Ilia Mirkin wrote:
> >
> > Hi Martin,
> >
> > Depends what your expectations are. Nouveau is missing a number of
> > features of the blob, the most important of whic
Hi Martin,
Depends what your expectations are. Nouveau is missing a number of
features of the blob, the most important of which is probably
stability. Whether you run into instability or not depends a lot on
the software that you use, so you'll just have to find out for
yourself if it works well
Hi Andre,
You're going to be best off filing a bug at
gitlab.freedesktop.org/drm/nouveau with some details of your setup:
1. lspci -nn -d 10de:
2. Your vbios (/sys/kernel/debug/dri/1/vbios.rom)
3. Your monitor's EDID, esp as reported when plugged into nouveau
(/sys/class/drm/card1-HDMI-1/edid or
I'm not saying this is wrong, but could you file a bug at
gitlab.freedesktop.org/drm/nouveau/-/issues and include the VBIOS
(/sys/kernel/debug/dri/0/vbios.rom)? That would make it easier to
review the full situation.
On Mon, Feb 14, 2022 at 11:03 AM Icenowy Zheng wrote:
>
> On PowerBook6,1
t 12:07 AM Nick Lopez wrote:
>
> If it’s correct I’d like to see it make its way upstream. I have no idea what
> the submission procedure is.
>
>
>
> From: Ilia Mirkin
> Sent: Thursday, January 20, 2022 11:24 AM
> To: Nick Lopez
> Cc: nouveau@lists.freedesktop.org
&g
This stuff is always so confusing. Let's think this through if
bios size is 4, and we're trying to read a 4-byte thing starting at
address 0, that _ought_ to work, I think. So in my strawman case,
bios->size == 4, and size == 4. So we should only error if size >
bios->size, not if they're ==.
Hey Jerry,
I'd look in the kernel log to see what's up. Perhaps the GPU hangs?
Cheers,
-ilia
On Fri, Nov 5, 2021 at 10:42 AM Jerry Geis wrote:
>
> Hi All,
>
> I am using Ubuntu 20.04 with VLC... normally the box boots up runs an plays
> videos just fien with about 20% usage for VLC
On Thu, Oct 14, 2021 at 12:51 PM Computer Enthusiastic
wrote:
>
> Hello,
>
> Thanks for the answer.
>
> On Wed, Oct 13, 2021 at 01:43:56PM -0400, Ilia Mirkin wrote:
> > The most straightforward thing, if you can reproduce at will, would be
> > to do a bis
The most straightforward thing, if you can reproduce at will, would be
to do a bisect to figure out which change this happened with. Once we
know which change caused the problem, it will hopefully provide with
more ability to sort out where we're going wrong. You can also play
with things like
On Fri, Oct 1, 2021 at 4:56 PM Jerry Geis wrote:
>
>
>
> On Fri, Oct 1, 2021 at 4:48 PM Jerry Geis wrote:
>>
>>
>>
>> On Fri, Oct 1, 2021 at 4:41 PM Ilia Mirkin wrote:
>>>
>>> On Fri, Oct 1, 2021 at 4:29 PM Jerry Geis wrote:
&g
On Fri, Oct 1, 2021 at 4:29 PM Jerry Geis wrote:
> yes very weird on the sound. Using analog speakers at the moment
> I got no test sound - and no video sound after getting nouveau to run
> correctly
> I was playing analog audio before ?
> Does nouveau only do HDMI audio ?
nouveau only
On Fri, Oct 1, 2021 at 3:58 PM Jerry Geis wrote:
>
>
>
> On Fri, Oct 1, 2021 at 3:40 PM Ilia Mirkin wrote:
>>
>> On Fri, Oct 1, 2021 at 3:36 PM Jerry Geis wrote:
>> >
>> >
>> >
>> > On Fri, Oct 1, 2021 at 3:27 PM Jerry Geis wrote:
On Fri, Oct 1, 2021 at 3:36 PM Jerry Geis wrote:
>
>
>
> On Fri, Oct 1, 2021 at 3:27 PM Jerry Geis wrote:
>>
>>
>>
>> On Fri, Oct 1, 2021 at 3:20 PM Ilia Mirkin wrote:
>>>
>>> On Fri, Oct 1, 2021 at 3:17 PM Jerry Geis wrote:
&
On Fri, Oct 1, 2021 at 3:17 PM Jerry Geis wrote:
> On Fri, Oct 1, 2021 at 3:06 PM Ilia Mirkin wrote:
>>
>> On Fri, Oct 1, 2021 at 3:00 PM Jerry Geis wrote:
>> > lsmod | grep nouveau
>> >
>> > What dont I have ?
>>
>> nouveau :)
>>
On Fri, Oct 1, 2021 at 3:00 PM Jerry Geis wrote:
> lsmod | grep nouveau
>
> What dont I have ?
nouveau :)
Other than that, you got everything...
Check dmesg for errors.
Cheers,
-ilia
On Fri, Oct 1, 2021 at 2:29 PM Jerry Geis wrote:
> Thanks perhaps this is part of the problem:
> ls -l /sys/kernel/debug/dri/
> total 0
This indicates that nouveau is not loaded. (Or loaded and failed
part-way through the load.)
Cheers,
-ilia
You can check the perf level your GPU is at, and potentially adjust it.
cat /sys/kernel/debug/dri/0/pstate
This should give a list of levels like "xx: stuff", with the "AC"
level being the current settings. Echo'ing any one of the xx's into
that file will attempt to switch to a different
Hi Joshua,
It looks like you got most of the way there. The BARs (BAR1 and BAR3)
are initialized by the code in nvkm/subdev/bar/gf100.c. As you can
see, this sets up a vmm per BAR, whose (physical address >> 12) is
written to 0x1704 / 0x1714. A vmm is basically a list of PDE's (and
the PTE lists
ay.
>
> Regards,
> Christian.
>
> Am 09.06.21 um 16:52 schrieb Ilia Mirkin:
> > Christian - potentially relevant is that Tegra doesn't have VRAM at
> > all -- all GTT (or GART or whatever it's called nowadays). No
> > fake/stolen VRAM.
> >
> > Cheers,
&g
Christian - potentially relevant is that Tegra doesn't have VRAM at
all -- all GTT (or GART or whatever it's called nowadays). No
fake/stolen VRAM.
Cheers,
-ilia
On Wed, Jun 9, 2021 at 10:18 AM Christian König
wrote:
>
> Hi Mikko,
>
> strange sounds like Nouveau was somehow also using the
Another instance of a report like this here:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/92
On Sat, Jun 5, 2021 at 3:53 PM Ondrej Zary wrote:
>
> Hello,
> I'm testing 5.13.0-rc4 and nouveau crashes with NULL pointer dereference in
> nouveau_bo_sync_for_device.
> Found various reports
Some trivia, no comment on the real logic of the changes:
On Fri, Apr 23, 2021 at 2:43 PM Lyude Paul wrote:
>
> Since AUX adapters on nouveau have their respective DRM connectors as
> parents, we need to make sure that we register then after their connectors.
then -> them
>
> Signed-off-by:
On Mon, Apr 12, 2021 at 4:01 PM Aaron Plattner wrote:
>
> On 4/12/21 12:36 PM, Roy Spliet wrote:
> > Hello Aaron,
> >
> > Thanks for your insights. A follow-up query and some observations
> > in-line.
> >
> > Op 12-04-2021 om 20:06 schreef Aaron Plattner:
> >> On 4/10/21 1:48 PM, Roy Spliet
On Tue, Mar 30, 2021 at 4:25 AM Karol Herbst wrote:
>
> On Tue, Mar 30, 2021 at 8:28 AM wrote:
> >
> > Hi,
> > I am currently the happy owner of a nforce 4 - SLI with two 7100gs graphics
> > cards setup.
> > Since I've read on your features matrix that such a setup is rather
> > uncommon among
On Thu, Mar 18, 2021 at 5:56 PM Lyude Paul wrote:
>
> Found this while trying to make some changes to the kms_cursor_crc test.
> curs507a_acquire checks that the width and height of the cursor framebuffer
> are equal (asyw->image.{w,h}). This is actually wrong though, as we only
> want to be
mained equal).
Signed-off-by: Ilia Mirkin
---
I did some basic testing with a patch to force the texture path to do
this conversion rather than to NV12, testing all 3 cases. However I need
to do better testing of edge cases, which I will do before pushing.
src/nouveau_xv.
The struct is giant, and triggers an order-7 allocation (512K). There is
no reason for this to be kmalloc-type memory, so switch to vmalloc. This
should help loading nouveau on low-memory and/or long-running systems.
Reported-by: Nathan E. Egge
Signed-off-by: Ilia Mirkin
Cc: sta
On Wed, Mar 3, 2021 at 8:25 AM Uwe Sauter wrote:
>
> Am 03.03.21 um 14:12 schrieb Ilia Mirkin:
> > On Wed, Mar 3, 2021 at 7:41 AM Alex Riesen
> > wrote:
> >>
> >> Ilia Mirkin, Sat, Feb 27, 2021 22:26:57 +0100:
> >>> Can you try Alex's p
On Wed, Mar 3, 2021 at 7:41 AM Alex Riesen wrote:
>
> Ilia Mirkin, Sat, Feb 27, 2021 22:26:57 +0100:
> > Can you try Alex's patch to modetest and confirm that you see issues
> > with modetest? If so, can you (and maybe Alex as well) try an older
> > kernel (I'm on 5.6) and
On Wed, Mar 3, 2021 at 5:30 AM Karol Herbst wrote:
>
>
>
> On Wed, Mar 3, 2021 at 11:07 AM Tomek LECOCQ wrote:
>>
>> Hello,
>>
>> I’ve already asked this on the Kernel Newbies mail list, but as developing
>> nouveau seems to be kind of similar to what I want to achieve, I thought it
>> would
On Sun, Feb 28, 2021 at 2:24 PM Uwe Sauter wrote:
> >> Summary:
> >> 5.4.101 | 5.10.19 | 5.11.2
> >> modetest-64 seems ok | seems ok | seems ok
> >> modetest-128 seems ok | seems ok | seems ok
> >> modetest-256 sliced | sliced | sliced
> >> X mouse
On Sun, Feb 28, 2021 at 12:59 PM Uwe Sauter wrote:
>
>
>
> Am 28.02.21 um 18:02 schrieb Ilia Mirkin:
> > On Sun, Feb 28, 2021 at 10:10 AM Uwe Sauter wrote:
> >>
> >>
> >>
> >> Am 27.02.21 um 22:26 schrieb Ilia Mirkin:
> >
On Sun, Feb 28, 2021 at 10:10 AM Uwe Sauter wrote:
>
>
>
> Am 27.02.21 um 22:26 schrieb Ilia Mirkin:
> > On Sat, Feb 27, 2021 at 7:28 AM Uwe Sauter wrote:
> >>
> >> I can also report that the modesetting ddx that comes with xorg-server
> >> 1
On Sat, Feb 27, 2021 at 7:28 AM Uwe Sauter wrote:
>
> Hi Ilia,
>
> Am 24.02.21 um 18:47 schrieb Ilia Mirkin:
> > On Wed, Feb 24, 2021 at 12:03 PM Alex Riesen
> > wrote:
> >>
> >> Ilia Mirkin, Wed, Feb 24, 2021 17:57:41 +0100:
> >>> On W
That's very surprising. As I recall, i2c-dev just adds /dev nodes for
various i2c devices (some of which would be exposed by nouveau, most
likely just the connector one to read EDID in your case, as temp/etc
sensors came later). It shouldn't cause nouveau to do anything
differently -- just allows
On Wed, Feb 24, 2021 at 12:03 PM Alex Riesen
wrote:
>
> Ilia Mirkin, Wed, Feb 24, 2021 17:57:41 +0100:
> > On Wed, Feb 24, 2021 at 11:53 AM Alex Riesen
> > wrote:
> > > Ilia Mirkin, Wed, Feb 24, 2021 17:48:39 +0100:
> > > > Just to be crystal clear -- ar
On Wed, Feb 24, 2021 at 11:53 AM Alex Riesen
wrote:
>
> Ilia Mirkin, Wed, Feb 24, 2021 17:48:39 +0100:
> > On Wed, Feb 24, 2021 at 11:35 AM Alex Riesen
> > wrote:
> > > Ilia Mirkin, Wed, Feb 24, 2021 16:10:57 +0100:
> > > > The fact that you're ge
On Wed, Feb 24, 2021 at 11:35 AM Alex Riesen
wrote:
> Ilia Mirkin, Wed, Feb 24, 2021 16:10:57 +0100:
> > The fact that you're getting lines with modetest means there's
> > something wrong with 256x256. What if you do 128x128 -- does that work
> > OK?
>
> Yes. Unfortu
[+emersion, -various people and lists who definitely don't care]
On Wed, Feb 24, 2021 at 4:09 AM Alex Riesen
wrote:
>
> Ilia Mirkin, Tue, Feb 23, 2021 19:13:59 +0100:
> > On Tue, Feb 23, 2021 at 11:23 AM Alex Riesen
> > wrote:
> > >
> > > $ xrandr
On Tue, Feb 23, 2021 at 11:23 AM Alex Riesen
wrote:
>
> Alex Riesen, Tue, Feb 23, 2021 16:51:26 +0100:
> > Ilia Mirkin, Tue, Feb 23, 2021 16:46:52 +0100:
> > > I'd recommend using xf86-video-nouveau in any case, but some distros
> >
> > I would like try this out.
On Tue, Feb 23, 2021 at 10:36 AM Alex Riesen
wrote:
>
> Ilia Mirkin, Tue, Feb 23, 2021 15:56:21 +0100:
> > On Tue, Feb 23, 2021 at 9:26 AM Alex Riesen
> > wrote:
> > > Lyude Paul, Tue, Jan 19, 2021 02:54:13 +0100:
> > > > diff --git a/drivers/gpu/drm/nou
On Tue, Feb 23, 2021 at 9:26 AM Alex Riesen
wrote:
>
> Lyude Paul, Tue, Jan 19, 2021 02:54:13 +0100:
> > diff --git a/drivers/gpu/drm/nouveau/dispnv50/disp.c
> > b/drivers/gpu/drm/nouveau/dispnv50/disp.c
> > index c6367035970e..5f4f09a601d4 100644
> > ---
ddx. Do I need to rebuild my initrd
> so it does not include the nouveau driver?
> Do I need to blacklist nouveau?
>
>
> Am 09.02.21 um 21:34 schrieb Ilia Mirkin:
> > I don't see any indication of a nouveau failure here. You could try
> > with the modeset ddx, perhaps the
turned off by the
> screensaver and back on when moving the mouse. I then stopped the X server.
>
> Please let me know if this test should be repeated with more verbose settings
> or if other log files are required, too.
>
>
> Regards,
>
> Uwe
>
>
> Am 0
The referenced issue is a context switching error / timeout. Is that
what you're seeing?
Is there anything in dmesg when the problem occurs? Can you reproduce
it by forcing the monitor to sleep (xset s off or equivalent)?
What you're describing sounds most like a display engine hang. Cursor
On Fri, Feb 5, 2021 at 6:45 PM Lyude Paul wrote:
>
> Get rid of the extraneous switch case in here, and just open code
> edp_backlight_mode as we only ever use it once.
>
> Signed-off-by: Lyude Paul
> ---
> .../gpu/drm/i915/display/intel_dp_aux_backlight.c | 15 ++-
> 1 file
ned-off-by: Simon Ser
> Reviewed-by: Lyude Paul
> Cc: Ben Skeggs
> Cc: Ilia Mirkin
> ---
> drivers/gpu/drm/nouveau/dispnv50/curs507a.c | 31 +++--
> 1 file changed, 28 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/dispnv50/cu
cted.
>
> v2:
> - Use drm_format_info instead of hardcoding bytes-per-pixel (Ilia)
> - Remove unnecessary size check (Ilia)
>
> Signed-off-by: Simon Ser
> Cc: Lyude Paul
> Cc: Ben Skeggs
> Cc: Ilia Mirkin
> ---
> drivers/gpu/drm/nouveau/dispnv50/curs507a.c | 21
tion is
> rejected.
>
> This commit depends on "drm/nouveau/kms/nv50-: Report max cursor
> size to userspace", otherwise mode_config.cursor_{width,height}
> is zero.
>
> Signed-off-by: Simon Ser
> Cc: Lyude Paul
> Cc: Ben Skeggs
> Cc: Ilia Mirkin
On Sat, Jan 23, 2021 at 6:09 PM o1bigtenor wrote:
>
> On Sat, Jan 23, 2021 at 12:52 PM Ilia Mirkin wrote:
> >
> > On Sat, Jan 23, 2021 at 1:40 PM o1bigtenor wrote:
> > >
> > > On Sat, Jan 23, 2021 at 10:55 AM Ilia Mirkin wrote:
> > > >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carlo Caione (1):
Don't advertise any PRIME offloading capabilities without acceleration
Ilia Mirkin (8):
nv4/exa: tiling is unsupported pre-nv10, reduce alignment requirements
dri2,present: move in pixmap before getting
On Sat, Jan 23, 2021 at 1:40 PM o1bigtenor wrote:
>
> On Sat, Jan 23, 2021 at 10:55 AM Ilia Mirkin wrote:
> >
> > On Fri, Jan 22, 2021 at 2:13 PM o1bigtenor wrote:
> > >
> > > On Fri, Jan 22, 2021 at 12:26 PM Ilia Mirkin wrote:
> > > snip
>
On Fri, Jan 22, 2021 at 2:13 PM o1bigtenor wrote:
>
> On Fri, Jan 22, 2021 at 12:26 PM Ilia Mirkin wrote:
> snip
> > Can you provide the output of "xrandr --verbose" before you've messed
> > around with anything like modelines/etc?
> >
>
> Its huge
On Fri, Jan 22, 2021 at 12:12 PM o1bigtenor wrote:
>
> On Fri, Jan 22, 2021 at 8:30 AM Ilia Mirkin wrote:
> >
> > On Thu, Jan 21, 2021 at 9:59 PM o1bigtenor wrote:
> > >
> > > Greetings
> > >
> > > Running a debian testing system
> >
On Thu, Jan 21, 2021 at 9:59 PM o1bigtenor wrote:
>
> Greetings
>
> Running a debian testing system
> $ uname -r
> 5.4.0-4-amd64
> with 2 graphics cards.
> The one I'm working on is a: GP 107 Nvidia GTX 1050 Ti
>
> Asus ROG GeForce GX 1050 Ti Strix-GTX1050 Ti with 2 - DVI plus 1 DP1.4
> and I
On Sun, Jan 3, 2021 at 1:25 PM Alexander Kapshuk
wrote:
>
> On Sun, Jan 3, 2021 at 7:20 PM Ilia Mirkin wrote:
> >
> > On Sun, Jan 3, 2021 at 3:18 AM Alexander Kapshuk
> > wrote:
> > >
> > > NVIDIA chip affected:
> > > 01:00.0 VGA compa
On Sun, Jan 3, 2021 at 3:18 AM Alexander Kapshuk
wrote:
>
> NVIDIA chip affected:
> 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce
> 210] (rev a1)
>
> The null pointer dereference occurs here:
> Thread 27 "vlc" received signal SIGSEGV, Segmentation fault.
> [Switching to
On Tue, Dec 29, 2020 at 10:52 AM Marc MERLIN wrote:
>
> On Sat, Dec 26, 2020 at 03:12:09AM -0800, Ilia Mirkin wrote:
> > > after boot, when it gets the right trigger (not sure which ones), it
> > > loops on this evern 2 seconds, mostly forever.
> >
> &
On Sun, Dec 27, 2020 at 12:03 PM Marc MERLIN wrote:
>
> This started with 5.5 and hasn't gotten better since then, despite some
> reports
> I tried to send.
>
> As per my previous message:
> I have a Thinkpad P70 with hybrid graphics.
> 01:00.0 VGA compatible controller: NVIDIA Corporation
On Mon, Dec 21, 2020 at 11:33 AM Kai-Heng Feng
wrote:
>
> [+Cc nouveau]
>
> On Fri, Dec 18, 2020 at 4:06 PM Takashi Iwai wrote:
> [snip]
> > > Quite possibly the system doesn't power up HDA controller when there's
> > > no external monitor.
> > > So when it's connected to external monitor, it's
Unfortunately this isn't a crash, but rather a warning that things are
timing out. By the time you get this, the display is most likely hung.
Was there anything before this, e.g. an error state dump perhaps?
What GPU are you using, what displays, and how are they connected?
What kind of
Hi Mark,
Presumably this is the same thing as the other thread you started,
which seemed to conclude with a working patch, and this email was just
stuck in the moderation queue?
Cheers,
-ilia
On Sun, Nov 29, 2020 at 6:02 PM Mark Hounschell wrote:
>
> I am not subscribed to this mailing list
When in doubt, blame nouveau.
I believe there has been some recent work around adjusting the logic
which checks that modes have enough bandwidth. Adding Lyude, who
worked on these changes. Not sure when they landed.
Klaus -- please supply a full Xorg log.
Cheers,
-ilia
On Sun, Nov 29, 2020
On Tue, Nov 3, 2020 at 1:08 PM Dave Stevenson
wrote:
>
> Hi Ilia
> Thanks again for the reply.
>
> On Wed, 28 Oct 2020 at 14:59, Ilia Mirkin wrote:
> >
> > On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson
> > wrote:
> > >
> > > Hi I
On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson
wrote:
>
> Hi Ilia
>
> Thanks for taking the time to reply.
>
> On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin wrote:
> >
> > The most common issue on arm is that the pci memory window is too narrow to
> >
The most common issue on arm is that the pci memory window is too narrow to
allocate all the BARs. Can you see if there are messages in the kernel to
that effect?
On Wed, Oct 28, 2020, 9:46 AM Dave Stevenson
wrote:
> Hi
>
> Seeing as we (Raspberry Pi) have just launched the Compute Module 4
>
This isn't meant to fix applications, it's meant to limit the range of
access to the buffer, for robustness/etc reasons. One would have to
look very carefully, as all this logic is rather tricky.
On Mon, Oct 19, 2020 at 4:07 AM Andrew Randrianasulu
wrote:
>
> Hi all!
>
> I saw TODO comment in
On Tue, Oct 13, 2020 at 8:01 AM Karol Herbst wrote:
>
> With this we try to detect if the endianess switch works and assume LE if
> not. Suggested by Ben.
>
> Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness
> failed")
> ---
> .../gpu/drm/nouveau/nvkm/engine/device/base.c
On Fri, Oct 9, 2020 at 5:54 PM Karol Herbst wrote:
>
> On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary wrote:
> >
> > Hello,
> > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working:
> > [0.00] Linux version 5.9.0-rc8+ (zary@gsql) (gcc (Debian 8.3.0-6)
> > 8.3.0, GNU ld (GNU
On Fri, Sep 25, 2020 at 6:08 PM Lyude Paul wrote:
>
> On Tue, 2020-09-22 at 17:22 -0400, Ilia Mirkin wrote:
> > On Tue, Sep 22, 2020 at 5:14 PM Lyude Paul wrote:
> > > On Tue, 2020-09-22 at 17:10 -0400, Ilia Mirkin wrote:
> > > > Can we use 6bpc on arbitrary DP m
On Thu, Sep 24, 2020 at 9:06 AM Roy Spliet wrote:
>
>
> Op 23-09-2020 om 22:36 schreef Karol Herbst:
> > On Wed, Sep 23, 2020 at 10:39 PM Jeremy Cline wrote:
> >>
> >> On Wed, Sep 23, 2020 at 09:02:45PM +0200, Karol Herbst wrote:
> >>> On Fri, Sep 11, 2020 at 6:21 PM Jeremy Cline wrote:
> >>
>
On Tue, Sep 22, 2020 at 5:14 PM Lyude Paul wrote:
>
> On Tue, 2020-09-22 at 17:10 -0400, Ilia Mirkin wrote:
> > Can we use 6bpc on arbitrary DP monitors, or is there a capability for
> > it? Maybe only use 6bpc if display_info.bpc == 6 and otherwise use 8?
>
> I don't thi
Can we use 6bpc on arbitrary DP monitors, or is there a capability for
it? Maybe only use 6bpc if display_info.bpc == 6 and otherwise use 8?
On Tue, Sep 22, 2020 at 5:06 PM Lyude Paul wrote:
>
> While I thought I had this correct (since it actually did reject modes
> like I expected during
On Sun, Sep 13, 2020 at 5:01 PM Tomasz Kłoczko wrote:
>
>
> On Sun, 13 Sep 2020 at 20:35, Ilia Mirkin wrote:
>>
>> What hardware are you using?
>
>
> :18:00.0 VGA compatible controller: NVIDIA Corporation GP104GL [Quadro
> P4000] (rev a1)
There's no accele
What hardware are you using?
On Sun, Sep 13, 2020 at 2:14 PM Tomasz Kłoczko wrote:
>
> Hi,
>
> I'm hitting that issue since Mesa 20.0.6 and it is present still in latest
> version 20.1.7
>
> ```
> [tkloczko@barrel SPECS]$ coredumpctl gdb 3926866
>PID: 3926866 (test_va_api)
>
On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy wrote:
> Any suggestions on how to trace the config issues? Do I have to debug the
> va_openDriver() function?
My guess, without reading any code, is that DRI_PRIME isn't doing what
you want it to, and the nouveau driver is being handed an intel
On Tue, Sep 1, 2020 at 3:31 AM Analabha Roy wrote:
>
> Hi,
>
> If I am reading the featurematrix right, VAAPI is supported for nouveau on
> the GeForce650M (my card).
>
> Here is the output of inxi -F
>
> System:Host: MediaServer Kernel: 5.4.0-42-generic x86_64 bits: 64
> Console: tty 1
The DDX eating CPU isn't intrinsically bad. Did you check where perf
says the CPU time is going? Could be doing copies/etc.
On Mon, Aug 17, 2020 at 12:52 AM Andrew Randrianasulu
wrote:
>
> I was testing Ilia's patches for ddx, and while they definitely helped for
> Xorg itself,
> qemu still
On Sun, Aug 16, 2020 at 8:20 AM Andrew Randrianasulu
wrote:
>
> В сообщении от Sunday 16 August 2020 07:20:18 Ilia Mirkin написал(а):
> > Well, if it's easy, try the patches I mailed to nouveau@ for the ddx.
>
> I applied patches manually (copy-pasted patches failed to
We don't really expect to have too many events in the queue. If there
are, then the algorithm we use isn't appropriate. Add a warning when the
queue gets very long, as it's an indication of something having gone
wrong.
Signed-off-by: Ilia Mirkin
---
src/drmmode_display.c | 11 +++
1
When drmWaitVBlank fails, make sure to remove the event from the queue.
Signed-off-by: Ilia Mirkin
---
Note this needs a bit more testing, and also double-checking what the
"correct" way of dealing with these errors is. I was able to trigger
errors with "xset dpms force of
a video was playing? If not, there's another path
for it to happen...
Cheers,
-ilia
On Thu, Aug 13, 2020 at 6:47 PM Ilia Mirkin wrote:
>
> I'm aware of this issue, and am experiencing it myself.
>
> The issue is that drmmode_event_handler takes up more and more CPU
> time. It
I'm aware of this issue, and am experiencing it myself.
The issue is that drmmode_event_handler takes up more and more CPU
time. It seems like some events are being "left behind". I haven't had
time to debug it further yet though.
I also have DRI3 enabled, but only very rarely do I make use of
All the present logic relies on EXA being used to wrap everything.
Unclear if present could even be used without the other things EXA
enables, but better be safe.
Signed-off-by: Ilia Mirkin
---
src/nv_driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/nv_driver.c b
This got broken with commit 86024cee back in 2014!
drmmode_pixmap/nouveau_pixmap expect there to be EXA wrapping around the
pixmap now, which is not there without accel.
Signed-off-by: Ilia Mirkin
---
src/drmmode_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src
a
> mess right now, here is a link to the program:
> https://github.com/EchelonX-Ray/ttygraphics . I'm just trying to learn
> about this and you really helped.
> On 7/5/20 7:17 PM, Ilia Mirkin wrote:
>
> Check fb_pan_display in drivers/video/fbdev/core/fbmem.c for the
> argument
e
> would make a difference.
>
> I really appreciate the help. I've been looking header files and a such
> trying to cobble together some information to figure this out. I hate
> to bother you with this because it seems slightly off topic.
>
> On 7/5/20 3:45 PM, Ilia Mirkin
h, because I just tried it again on a
> dell laptop with Intel HD Graphics 4400 to the same failure.
>
> On Jul 5, 2020 12:35, Ilia Mirkin wrote:
>
> Are you setting the overallocation to 200?
>
> On Sun, Jul 5, 2020 at 3:41 AM Michael T. Kloos
> wrote:
> >
> > Does N
Are you setting the overallocation to 200?
On Sun, Jul 5, 2020 at 3:41 AM Michael T. Kloos
wrote:
>
> Does NOUVEAU support mmaping a double-sized Framebuffer?
> When attempting to run, where fd refers to "/dev/fb0":
>
> mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
>
> I
You probably have drm.debug set to something.
On Tue, Jun 23, 2020 at 4:42 AM Mathieu Malaterre wrote:
>
> Hi there,
>
> I am gettings tons of messages in dmesg output such as:
>
> [...]
> [ 2419.238990] [drm:drm_mode_addfb2 [drm]] [FB:65]
> [ 2419.243388] 00a0 2 base507c_ntfy_set
> [
1 - 100 of 1335 matches
Mail list logo
