Ping! Hi again,
After some code review, I just found set_phys_mem command for ioctl
was missing in kqemu_ioctl() from original kqemu-freebsd.c and my
porting kqemu-dragonfly.c
(kqemu never work correctly under *BSD ?)
Anyway, I updated kqemu module,but still kqemu does not give me any benefit.
S
On Mon, Apr 13, 2009 at 04:57:55PM +0200, Erik Wikstr?m wrote:
> On 2009-04-13 15:10, Joerg Sonnenberger wrote:
> > On Mon, Apr 13, 2009 at 03:28:23PM +0300, Hasso Tepper wrote:
> >> The problem is that there is too many packages with common problem (for
> >> DragonFly) - they don't include unistd
Now that I'm in the same room with the machine, here's the messages I've
been seeing when trying to play audio CDs on a current dragonfly system,
intel chipset motherboard w P4 processor, pcm, snd_ich and joy devices
added to the generic kernel. MAKEDEV'd snd0, acd1 and cd1
when trying "cdcon
On 2009-04-13 15:10, Joerg Sonnenberger wrote:
> On Mon, Apr 13, 2009 at 03:28:23PM +0300, Hasso Tepper wrote:
>> The problem is that there is too many packages with common problem (for
>> DragonFly) - they don't include unistd.h, but compile regardless of that
>> on Linux, NetBSD and FreeBSD, se
On Mon, Apr 13, 2009 at 03:28:23PM +0300, Hasso Tepper wrote:
> The problem is that there is too many packages with common problem (for
> DragonFly) - they don't include unistd.h, but compile regardless of that
> on Linux, NetBSD and FreeBSD, seems. Many of such packages are C++. Maybe
> there i
Hasso Tepper wrote:
> * There is major problem with DragonFly that too many packages need
> patching to include unistd.h - especially stuff using C++, but C
> packages as well. This might be right thing to do, but I still would
> like to avoid it. Any ideas?
As two persons already asked, I d
On Mon, 13 Apr 2009 08:39:07 +0300
Hasso Tepper wrote:
> pkgsrc bulk build report
>
>
> DragonFly 2.3/i386
> Compiler: gcc
>
> Build start: 2009-04-08 05:12
> Build end: 2009-04-13 02:37
>
> Full report:
> http://leaf.dragonflybsd.org/~hasso/pbulk-logs/20090408.0512/
G.Isenmann wrote:
> Hi, would it be possible to include these small patches into R13B? I
> believe they have no side effect on other platforms and improve the
> situation on dragonfly.
As far as I can see these were included in R13B with small problem ;).
> CC dragonfly-users:
> - The first patc
A short list of problems based on first bulk build ...
* It introduced some new _POSIX defines in unistd.h which are clearly
wrong for us - _POSIX_BARRIERS and _POSIX_SPIN_LOCKS are such examples.
I hope that Peter will fix these ASAP, but ...
Although libthread_xu implements barriers, w
