On 10/06/12(Sun) 16:53, Jan Stary wrote:
> On Jun 10 13:42:28, Martin Pieuchot wrote:
> > On 10/06/12(Sun) 12:51, Jan Stary wrote:
> > > I got this Mac Mini on my hands, and I would like to install
> > > current/macppc on it. According to
> > > http://www.openbs
On 11/06/12(Mon) 20:23, Jan Stary wrote:
> > > > > I got this Mac Mini on my hands, and I would like to install
> > > > > current/macppc on it. According to
> > > > > http://www.openbsd.org/macppc.html#hardware
> > > > > the following MicMini's are supported:
> > > > >
> > > > > Mac mini (Po
On 21/06/12(Thu) 19:27, Peter J. Philipp wrote:
> Hi,
>
> Since deraadt mentioned the names of people who left to bitrig and I'm
> wondering what will happen to the macppc port? Is it going to go the
> route of the mac68k port too? I saw some commits earlier on it so that
> got my hopes up...
On 17/08/12(Fri) 14:51, Artturi Alm wrote:
> Hi,
>
> Bugs section of ugen(4) up to date? or does devel/libusb1
> support reads from isochronous endpoints by mistake?
It "supports" reads from isochronous endpoints mainly because the
interface is the same as for bulk and interrupts ones, and in the
On 27/08/12(Mon) 10:25, Gregory Edigarov wrote:
> Hi,
>
> with yesterday's current X failed to start with segfault using intel
> driver. vesa works, but spectrwm is failng to load too, again with segfault.
> is there some massive changes undergoing, or is that just some
> temporary regression?
On 04/10/12(Thu) 22:44, matt wrote:
> I assume I or my hardware is doing something stupid and obvious.
> I've been trying to successfully build OpenBSD for the first time on
> a 2002 G4 (Mirror Drive Door) dual 1ghz. The RAM is new, and
> slightly faster than the bus speed demands (pc3200 instead o
On 11/10/11(Tue) 11:07, Brynet wrote:
> Antoine Jacoutot wrote:
> > mpi has a port of libusb 1.0 which I am actually putting under tests.
>
> I'd be interested in testing this, does he plan on submitting it to ports@?
Of course, what a question ;)
But for the moment the port, or more precisely t
On 14/10/11(Fri) 23:04, Bryan wrote:
> I began noticing this error message when I was using my Kensington
> Trackball. I'd be in Chrome, accessing webpages, and typing inside
> text boxes (much like the GMail one I'm typing into now). All of a
> sudden, it was as if someone had enabled some kind o
201 - 208 of 208 matches
Mail list logo
