similar to: Place of functional levels in Samba4 roadmap

Subject: [PATCH] drm/nv04: fix null pointer dereferences of native_mode nv_connector->native_mode is not set when no modes were found for the connector, so its existence can't be assumed. In nv04_dfp_mode_fixup, reject the mode if GPU scaling is enabled but native mode is not known. In nv04_dfp_mode_set, use clock value from nv_encoder->mode instead of nv_connector->native_mode. If

http://bugs.freedesktop.org/show_bug.cgi?id=23295 Summary: nouveau KMS: null pointer dereference if native mode is not found Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

http://bugs.freedesktop.org/show_bug.cgi?id=23373 Summary: X goes to 100% cpu on start with GeForce 9400 (0x086a, C79) Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

http://bugs.freedesktop.org/show_bug.cgi?id=13481 Summary: RandR12 fails on GF6600Go Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: anssi

Hi all, the following patch fixes a race-condition in the nouveau ddx which caused frequent x-server crashes for at least 1 user under some loads when OpenGL triple-buffering is enabled, which it is by default on XOrg 1.12 and later. As a side effect, it provides a small optimization for the common case of bufferswap at next vblank. The other way to avoid the race + possible crash is to set

Firmware files in firmware/ directory are not expected to be in binary format. The nouveau files are in binary format, and are therefore removed when running e.g. make clean. Fix that by converting them to ihex format instead. The patch is really big as it contains the ctxprogs stuff, so I'll provide a link instead:

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

Hi I tried building Mandrake 9.2 DVD (combine files from iso images and so on). Then I tried to boot it in MS Virtual PC 2004 and it didn't work. After a while of expirementing I found out that no images work. Attached is sample cd image. (Made with Nero 6.3). I wonder is the problem in Nero, Virtual PC or in syslinux? isolinux-debug.bin gives following messages: --- ISOLINUX 2.08

Hi, I'm a new Speex list member, and so far I'm very impressed with Speex. BUT automatic gain control seems to me to be virtually unusable. If a recorded utterance begins with even a tiny noise, that noise is amplified to the maximum volume. (See, e.g. the initial utterance in the TIMIT corpus, "She kept your dark suit...") This seems like a bug to me. If list members

On May 10, 2018, at 1:33 AM, Karanbir Singh <kbsingh at centos.org> wrote: > > I am pleased to announce the general availability of CentOS Linux 7 > (1804) for across all architectures. I?ve checked about a dozen of the mirrors, and see no *.torrent files yet. Any idea how long they?ll take to appear? I ask because we?re building a system today, so if it?s going to be more than

On 05/10/2018 09:10 AM, Warren Young wrote: > On May 10, 2018, at 1:33 AM, Karanbir Singh <kbsingh at centos.org> wrote: >> >> I am pleased to announce the general availability of CentOS Linux 7 >> (1804) for across all architectures. > > I?ve checked about a dozen of the mirrors, and see no *.torrent files yet. Any idea how long they?ll take to appear? I ask

How about using the existing OpenSSH client's PKCS#11 support to isolate keying material in a dedicated process? A similar approach, "Practical key privilege separation using Caml Crush", was discussed at FOSDEM'15 with a focus on Heatbleed [1][2] but the ideas and principles are the same. Now this is easily done using the following available components: - SoftHSM to store

http://bugs.freedesktop.org/show_bug.cgi?id=15502 Summary: Unknown LVDS configuration bits Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: low Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pee at

http://bugs.freedesktop.org/show_bug.cgi?id=26193 Summary: nouveau falls back to NoAccel on 9400M Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: bjt23

http://dovecot.org/roadmap.html I'll try to keep it updated. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071230/4cfeacec/attachment-0002.bin>

I can't find any R roadmap. Is it available somewhere ? Etienne -- View this message in context: http://www.nabble.com/Roadmap---tp21791647p21791647.html Sent from the R devel mailing list archive at Nabble.com.

Are there anyone who has a machine on which the *current* version of SYSLINUX ends up with an inoperable USB keyboard, especially when using the menu system? I might have a workaround, but I don't have a system which exhibits the problem available to me at the moment, and I really don't want to put in a hack without knowing that it actually does anything... If you do have such a

On 21 Mar 2015, at 10:14, Florian Sager <sager at agitos.de> wrote: > > Hi Timo, > > congrats to the merger with OX. > > Currently the implementation of RFC 5257, ANNOTATE-EXPERIMENT-1, has > only low priority on http://wiki2.dovecot.org/Roadmap > I want to explain a scenario that would benefit from annotation support > to - maybe - increase the priority in your

On Sun, 2018-05-06 at 22:14 +0200, Davy Defaud via samba wrote: > > So, what’s the current status now? I can see RODC and SUBDOMAIN on the > roadmap. > But, as there are not “FUNDED”, is there someone actually working on it? > If so, are they targeted for a particular version or just “when it’s ready”? RODC support has been funded as is pretty good as of 4.8. There are still some

Hi all... I'm looking once again at the Syslinux roadmap. It seems to me that we're going to have a very hard time making Syslinux 4.00 be the full-featured everything-in-C release I had hoped for, or perhaps more specifically, that it is justifiable to sit on the current filesystems-in-C code waiting for the rest. That would probably mean productizing the transitional COM32R module