Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Feb 2011 07:00:22 GMT
From:      John Wehle <john@feith.com>
To:        freebsd-emulation@FreeBSD.org
Subject:   Re: kern/149168: [linux] [patch] Linux sendmsg / recvmsg / etc fixes for pulseaudio
Message-ID:  <201102280700.p1S70MFE012715@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/149168; it has been noted by GNATS.

From: John Wehle <john@feith.com>
To: avg@freebsd.org
Cc: rdivacky@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/149168: [linux] [patch] Linux sendmsg / recvmsg / etc fixes for pulseaudio
Date: Mon, 28 Feb 2011 02:57:26 -0500 (EST)

 > Unfortunately, with this patch (unlike its original version) linux skype no
 > longer connects to FreeBSD pulseaudio daemon for me on CURRENT/amd64.
 > So something important seems to have been lost or broken while making the
 > improvements.
 
 That's a bit strange.  The amd64 specific bits are for capget / capset
 which are only used if you're running the Linux pulseaudio daemon,
 they're not used by the client code so I don't suspect a problem
 there.
 
 The rest of the code works fine (at least under light use) on my
 FreeBSD 8.2 i386 machine. The only changes between this patch and
 the previous are:
 
   a) Mucking linux/syscalls.master in i386 & amd64 ... unlikely
      to be a problem.
 
   b) "Cosmetic" change to linux_to_bsd_msghdr / linux_sendmsg to
      also ignore msg_controllen.  The change was unnecessary and
      rather minor, however it made the msg_controllen handling
      more symmetrical.
 
      Not sure what would have work on the i386 and not amd64 in what
      I mucked. :-(
 
 Are you sure the problem is with the later patch?  Did anything else
 change in your environment?  Does paplay work?  If not, what does
 paplay / pulseaudio daemon debug report?
 
 I'm not setup with CURRENT or amd64 ... how do you want to proceed?
 Do you want to provide access to a CURRENT/amd64 machine that I
 can reboot / muck the kernel?  Do you want to debug this?  Should
 I invest in setting up FreeBSD CURRENT/amd64 running under QEMU / Virtualbox?
 
 Don't mean to be asking too many questions. :-)  Just interesting in
 the game plan.
 
 -- John
 -------------------------------------------------------------------------
 |   Feith Systems  |   Voice: 1-215-646-8000  |  Email: john@feith.com  |
 |    John Wehle    |     Fax: 1-215-540-5495  |                         |
 -------------------------------------------------------------------------
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201102280700.p1S70MFE012715>