diff options
author | Thomas Schwinge <thomas@schwinge.name> | 2012-03-20 22:45:31 +0100 |
---|---|---|
committer | Thomas Schwinge <thomas@schwinge.name> | 2012-03-20 22:45:31 +0100 |
commit | 03f16b2498fa93bd69da9baa6d45d29f08bea45e (patch) | |
tree | f5944c96b594488ea7ac942b7b891c6e8f43bd2e | |
parent | 9a1cf9275937cd7a368da02b5b58d92bc362d9de (diff) | |
parent | a65f14df8e3d93f71acf276fb0773d6557b9fbab (diff) |
Merge remote-tracking branch 'fp/master'
-rw-r--r-- | open_issues/boehm_gc.mdwn | 11 | ||||
-rw-r--r-- | open_issues/glibc.mdwn | 2 | ||||
-rw-r--r-- | open_issues/wayland.mdwn | 33 |
3 files changed, 46 insertions, 0 deletions
diff --git a/open_issues/boehm_gc.mdwn b/open_issues/boehm_gc.mdwn index e7f849f2..ca2063a5 100644 --- a/open_issues/boehm_gc.mdwn +++ b/open_issues/boehm_gc.mdwn @@ -321,3 +321,14 @@ It has last been run and compared on 2010-11-10, based on CVS HEAD sources from <pinotree> hmm... <pinotree> apparently enabling MMAP_ANON in mono's libgc copy was a good step, let's see + + +### IRC, OFTC, #debian-hurd, 2012-03-18 + + <pinotree> youpi: mono is afflicted by the SIGUSR1/2 conflict with libgc + <youpi> pinotree: didn't we have a solution for that? + <pinotree> well, it works just for one signal + <pinotree> the ideal solution would be having a range for RT signals, and + make libgc use RTMIN+5/6, like done on most of other OSes + <youpi> but we don't have RT signals, do we? + <pinotree> right :( diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn index 3160c86f..943f44bb 100644 --- a/open_issues/glibc.mdwn +++ b/open_issues/glibc.mdwn @@ -210,6 +210,8 @@ Last reviewed up to the [[Git mirror's d40c5d54cb551acba4ef1617464760c5b3d41a14 * `sys/epoll.h` + Used by [[wayland]], for example. + * `sys/eventfd.h` * `sys/inotify.h` diff --git a/open_issues/wayland.mdwn b/open_issues/wayland.mdwn new file mode 100644 index 00000000..67f78b1d --- /dev/null +++ b/open_issues/wayland.mdwn @@ -0,0 +1,33 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_porting]] + +IRC, freenode, #hurd, 2012-03-18: + + <antrik> Wayland should be very portable. all the system dependencies are + in the infrastructure, such as DRI + <antrik> we have had a DRI task (for X.Org) for years + <antrik> (in fact I would be the right person to implement this, + considering my background -- by quite frankly, I doubt I'll ever do it) + <tschwinge> http://xorg.freedesktop.org/wiki/Hurd_Porting + +IRC, freenode, #hurd, 2012-03-20: + + <youlysses> Is wayland something that will be semi-easy to port to the + hurd? I saw GNOME is heading in this direction. + <pinotree> wayland at the moment is linux only + <tschwinge> youlysses: A DRI implementation will be needed. + <pinotree> that, and libdrm compiling + <youlysses> So it will take some work ... but theres no *HUGE* design + decison that would inhibit it? + <pinotree> i know it uses epoll, for instance + <tschwinge> youlysses: I cannot judge how complex a DRI system is, and how + much needs to be designed vs. implemented. |