On Tue, 2014-10-21 at 16:23 -0700, Geoff Levand wrote:
> X-Debbugs-CC: Benjamin Herrenschmidt
>
> Hi,
>
> On Tue, 2014-10-21 at 09:41 -0200, Breno Leitao wrote:
> > Hi Geoff,
> >
> > Any status about this bug?
>
> This is caused by the altivec optimiz
On Tue, 2011-03-08 at 13:00 +0100, Michel Dänzer wrote:
> On Die, 2011-03-08 at 07:30 +1100, Benjamin Herrenschmidt wrote:
> > On Mon, 2011-03-07 at 10:45 +0100, Michel Dänzer wrote:
> > >
> > > I've been using radeon KMS on my PowerBook ever since I got it w
The uninorth AGP driver doesn't allow AGP transfer rates beyond
> 1x to work reliably with KMS. Benjamin Herrenschmidt (CC'd) was
> working on a fix for this, any progress Ben?
I have hacks. But I never got it working reliably. In fact, on the
laptop I have here, even
On Thu, 2009-01-08 at 21:57 +0100, Wolfgang Kroener wrote:
> Hi,
> On Wed, Oct 01, 2008 at 08:10:10, Benjamin Herrenschmidt wrote:
> > Can you resend it with a proper Signed-off-by: line ? Thanks !
>
> I think the mail (http://lkml.org/lkml/2008/10/1/134) got lost
> some
On Mon, 2007-07-30 at 20:41 +0200, Stephane Louise wrote:
> Bonjour Ben, merci pour le suivit.
>
> Benjamin Herrenschmidt a écrit :
> > Does this happen also without radeonfb and with X alone using the X
> > "radeon" driver ?
>
> Yes, unless I misunderstan
The log is incomplete... looks like the bcm43xx driver is so verbose, it
kicked useful things out. Thus I can't see the output from the video
driver which is the interesting bit...
Also, is it nvidiafb or rivafb ?
Cheers,
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
> Console: switching to colour frame buffer device 210x65
> radeonfb (:00:10.0): ATI Radeon Yb
> Generic RTC Driver v1.07
> Macintosh non-volatile memory driver v1.1
> serial8250_init: nothing to do on PowerMac
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <[EMAIL PROTECTED]>)
Package: pbbuttonsd
Version: 0.7.9-2
Severity: normal
The scripts shipped with pbbuttons will cause it to issue a
hdparm -p /dev/device
(device is typically hda or whatever ide device is there)
I think this used to trigger an "autotune" of the interface, but current
hdparm instead sends the ke
On Mon, 2007-01-22 at 16:05 +0100, Matthias Grimm wrote:
> On Mon, 22 Jan 2007 14:33:35 +1100
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> > > Which solution you prefer is up to you but I would be glad if at least
> > > solution #1 could be realised.
> This will allow modern systems to be compiled only with
> CONFIG_PMAC_BACKLIGHT and a user space daemon does the rest. I hope my
> point could be seen. I would really appreciate if the configuration
> could be cleaned up.
>
> Other solutions could be:
>
> 2. If the sysfs backlight driver is ope
On Thu, 2006-11-30 at 23:04 +0100, Étienne Bersac wrote:
> Hi,
>
> Beware not to confuse iMac G5 rev A&B and rev C (among PowerMac G5).
> iMac G5 rev C (chip PowerMac 12,1) do not have yet their windfarm
> driver. Benh told that he began the work on this driver but has
> difficulties to get access
On Thu, 2006-10-26 at 19:25 +0100, Roger Leigh wrote:
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>
> >> I found a solution to the problem. Adding
> >>
> >> Option "PanelSize" "1680x1050"
> >> Option &q
> I found a solution to the problem. Adding
>
> Option "PanelSize" "1680x1050"
> Option "MonitorLayout" "TMDS,NONE"
>
> made the display work correctly. IIRC this was needed with XOrg 6.9,
> but wasn't needed with 7.0 (because it was intelligent enough to
> autodetect correctly
On Mon, 2006-09-25 at 11:25 +0100, Roger Leigh wrote:
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>
> > What monitor model is it precisely ?
>
> It's a 2005 Aluminium 20" Cinema Display. Model No. A1081 according
> the bottom edge. It has built
On Mon, 2006-09-25 at 10:02 +0200, Michel Dänzer wrote:
> Yes, although it might also make sense to try the current master and
> ati-1-0-branch heads.
>
> > I tried this out. All revisions built OK, but all caused the monitor to
> > power off.
> >
> > Installing the old xserver-xorg-core and xs
http://people.freedesktop.org/~airlied/radeon_rn50_memmap.diff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, 2006-06-11 at 20:31 +0200, Michel Dänzer wrote:
> On Sun, 2006-06-11 at 20:14 +0200, Wolfgang Pfeiffer wrote:
> > On Sun, Jun 11, 2006 at 01:34:52PM +0200, Michel Dänzer wrote:
> > >
> > > Does the attached patch help with Option "UseFBDev"?
> >
> > Yes. :))) ... Thanks a lot, Michel ...
On Thu, 2006-06-08 at 11:48 +0200, Michel Dänzer wrote:
> On Wed, 2006-06-07 at 23:31 +0200, Wolfgang Pfeiffer wrote:
> > On Wed, Jun 07, 2006 at 11:09:43AM +0200, Michel Dänzer wrote:
> > > On Mon, 2006-06-05 at 20:05 +0200, Wolfgang Pfeiffer wrote:
> > > >
> > > > [ 136.378439] [drm] Setting G
On Tue, 2006-02-14 at 20:16 +0200, Martin-Éric Racine wrote:
>
> Ben: would you know why this only seems to affect PowerMac users?
No, no idea, might indeed be an endian bug
Ben.
On Tue, 2006-02-14 at 20:16 +0200, Martin-Éric Racine wrote:
> ti, 2006-02-14 kello 23:14 +0700, Eugene Konev kirjoitti:
> > 1. The correct way to use gpm with X server with /dev/input/mice in
> >linux 2.6 is _not_ use gpm repeater, as kernel driver is perfectly
> >capable to multiplex even
> > So I think it's udev that is broken (version 0.074-2 from sid)
>
> Could you report a bug to udev's maintainer?
I just upgraded to 0.074-3 and the problem seems to be fixed
[EMAIL PROTECTED]:~$ ls -l /dev/input/
total 0
crw-rw 1 root root 13, 64 2005-11-19 11:30 event0
crw-rw 1 ro
On Fri, 2005-11-18 at 11:20 +0100, Marcus Better wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Yves-Alexis Perez wrote:
> > Events are dynamically created/deleted
> > by udev, and they start at 0. But maybe this is a kernel bug, or udev bug..
>
> No, I think it is perfectly OK. inp
On Fri, 2005-11-18 at 12:15 -0200, Otavio Salvador wrote:
> Marcus Better <[EMAIL PROTECTED]> writes:
>
> > Hello,
> >
> > I am the maintainer of input-utils. A user reported a problem (bug
> > #326149) on the powerpc architecture that I need some help
> > investigating, since I don't have a ppc m
Package: libc6
Version: 2.3.5-6
Severity: normal
ppc32 glibc has a problem when running with a ppc64 kernel with 64k
pages support enabled. This is fixed in upstream glibc CVS already (64k
pages support isn't yet available in the released kernels, but I'll
release the patch soon and it would be u
Package: wesnoth
Version: 0.9.5-1
Severity: normal
Battle for Wesnoth v0.9.5
Started on Fri Aug 19 16:26:06 2005
started game: 3446302398
terminate called after throwing an instance of 'zipios::FCollException'
what(): Unable to find zip structure: End-of-central-directory
Aborted
-- Syst
The bug has been fixed in gcc (though it may not have hit 3.4 CVS yet).
See debian #307993 for details. This bug was causing any arch to die
when building glibc with -g1, it's a gcc 3.4 regression, and now that
it's fixed, it should be possible to switch the 2.3.5 package to gcc 3.4
(well, at least
Ok, the bug has been fixed. It was causing any architecture to die on
NPTL build with -g1 with 3.4. The patch below should be applied on
debian's 3.4 package asap so we can start using it for building
experimental glibc :)
http://gcc.gnu.org/ml/gcc-patches/2005-05/msg00685.html
Ben.
--
To UN
> > gcc-3.4 tst-fini1mod.c -c -std=gnu99 -O2 -O3 -Wall -Winline
> > -Wstrict-prototypes -Wwrite-strings -fstrict-aliasing -g -g1 -pipe
> > -mnew-mnemonics
> > -fpic-I../include -I.
> > -I/home/benh/glibc-2.3.5/build-tree/powerpc-nptl/nptl -I.. -I../libio
> > -I/home/benh/glibc-2.3.5/buil
On Sat, 2005-05-07 at 09:05 +0200, Matthias Klose wrote:
> Ubuntu currently builds glibc-2.3.5 with gcc-3.4 CVS 20050209, that's
> older than the Debian gcc-3.4 CVS 20050314. Jeff, any hints?
>
> I'll update gcc-3.4 to the current CVS once -13 enters testing.
I doubt current CVS fixes it (from th
On Sat, 2005-05-07 at 09:05 +0200, Matthias Klose wrote:
> Ubuntu currently builds glibc-2.3.5 with gcc-3.4 CVS 20050209, that's
> older than the Debian gcc-3.4 CVS 20050314. Jeff, any hints?
>
> I'll update gcc-3.4 to the current CVS once -13 enters testing.
OK. It would be interesting if ubuntu
Bug 307985 is actually caused by this lack of NTPL. I've tried building
it here but got a gcc ICE, see comments in that other bug.
This one can probably be marked as dup.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, 2005-05-07 at 02:39 -0400, Daniel Jacobowitz wrote:
> > Looks like our gcc-3.4 isn't quite there yet ...
>
> Huh. I've never seen that one before; yeah, file a bug, I suppose.
Just did, it's debian bug #307993
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubsc
On Sat, 2005-05-07 at 01:37 -0400, Daniel Jacobowitz wrote:
> /usr/bin/gcc still doesn't have PPC TLS support. Does glibc default to
> using 3.4 nowadays? Smart choice I guess.
>
> I think that's right but I haven't looked at the packaging in about a
> year now.
>
gcc-3.4 tst-fini1mod.c -c -st
> /usr/bin/gcc still doesn't have PPC TLS support. Does glibc default to
> using 3.4 nowadays? Smart choice I guess.
I got bitten by that :) glibc package rule is hard coded to gcc-3.3
which doesn't do __thread. I just changed it to gcc-3.4 and restarted
the build, news in about 1h...
> I thin
> These symbols are part of NPTL cancellation handling. They won't work
> unless you run with NPTL.
I figured that out yes. NPTL isn't enabled for powerpc glibc, it should
be with 2.3.5. I'm trying to make a build, but my lack of knowledge of
the debian package build files don't make that simple
On Fri, 2005-05-06 at 23:09 -0400, Daniel Jacobowitz wrote:
> On Sat, May 07, 2005 at 12:42:02PM +1000, Benjamin Herrenschmidt wrote:
> > Package: libc6
> > Version: 2.3.5-1
> > Severity: normal
> >
> >
> > The 2.3.5-1 ppc build present in experimental ha
Package: libc6
Version: 2.3.5-1
Severity: normal
The 2.3.5-1 ppc build present in experimental has a problem with
libpthread-0.10.so binary. For some reason I haven't been able to
explain, it lacks the version GLIBC_2.3.3 symbol (it does have 2.3.2
and 2.3.4 and libc6 itself has them all).
This
Package: libc6
Version: 2.3.5-1
Severity: normal
glibc should be built with TLS/NPTL for ppc nowadays, since we finally
get a recent enough version (it was implemented upstream years ago and
other major distros had it for some time now).
-- System Information:
Debian Release: 3.1
APT prefers u
On Mon, 2005-04-25 at 12:17 +0200, Michael Schmitz wrote:
> > > offset 0 rc 16 buf.sig 90 buf.len 2 buf.name >nvram<
> > > offset 32 rc 16 buf.sig 95 buf.len 62 buf.name >system<
> > > offset 1024 rc 16 buf.sig 112 buf.len 193 buf.name >common<
> > > offset 4112 rc 16 buf.sig 160 buf.len 82 buf.nam
On Fri, 2005-04-22 at 18:41 +0200, Michael Schmitz wrote:
> > Hi,
> >
> > Here is the output of lsprop /proc/device-tree
> >
> > name "device-tree"
> > model"Power Macintosh"
> > compatible "AAPL,e407"
> >
On Thu, 2005-03-17 at 01:07 +, Scott James Remnant wrote:
> On Thu, 2005-03-17 at 01:57 +0100, Andreas Jochens wrote:
>
> > On 05-Mar-17 00:10, Scott James Remnant wrote:
> > > No, I would just prefer consistency. You've deliberately chosen an
> > > architecture name that's jarringly differen
On Wed, 2005-03-16 at 22:24 +, Scott James Remnant wrote:
> On Wed, 2005-03-16 at 23:14 +0100, Andreas Jochens wrote:
>
> > On 05-Mar-16 22:01, Scott James Remnant wrote:
> > > On Wed, 2005-03-16 at 22:48 +0100, Andreas Jochens wrote:
> > >
> > > My concern is the same as that of the Project
> However, I still do not understand why you and/or the Project Leader
> want to override the decision of the porters and choose a different name
> than the LSB specifies. I am not saying that Debian should always follow
> the LSB blindly, but I cannot see a good reason for deviating from the
>
> Anyway, the biarch approach will also need a 'dpkg' which supports
> separate 64-bit ppc64 packages in the end.
>
> What are your concerns? Do you refuse to support a native 64-bit
> powerpc64/ppc64 port? Or do you want a different name for it?
I think there is not real point in doing so, or
On Wed, 2005-03-16 at 20:27 +0100, Andreas Jochens wrote:
> Hello,
>
> This is a call for help from the 'ppc64' porters.
>
> On 05-Mar-14 16:14, Martin Michlmayr wrote:
> > Also, as with the amd64 port, there is disagreement about the name.
> > While ppc64 would be nicer and in line with the LSB
On Wed, 2005-03-09 at 09:07 +, Francois wrote:
> On Tue, 2005-03-08 at 22:48, Benjamin Herrenschmidt wrote:
> > On Tue, 2005-03-08 at 17:04 +, Francois wrote:
> > >
> > > thanks for your help. I've tried again and I've explicitly selected
> >
I can find. I'm a bit busy atm...
>
> With regards to memory, top reports 13MB virtual, of which 5.4MB is
> shared. The only obvious place I can think of offhand to reduce the
> memory footprint is to use a lightweight xml library instead of libxml2,
> but since libxml2 is shared m
On Fri, 2005-02-18 at 08:59 +0100, Jérôme Marant wrote:
> Quoting Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
>
> > Ok, I tried 21.3+1-6 (-7 wasn't built for ppc it seems) and the problem
> > is the same. My ISO_Level3_Shift key is sort-of interpreted by emacs as
&
On Sat, 2005-02-19 at 15:01 +0100, Denis Barbier wrote:
> [Sorry for breaking this thread, but I am back from vacation and
> the nameserver for my mail is down for the whole weekend]
>
> Benjamin, I cannot reproduce this bug; as emacs does not handle
> ISO_Level3_Shift, my only bet is that somethi
On Fri, 2005-02-18 at 11:41 +1100, Benjamin Herrenschmidt wrote:
> Ok, I tried 21.3+1-6 (-7 wasn't built for ppc it seems) and the problem
> is the same. My ISO_Level3_Shift key is sort-of interpreted by emacs as
> beeing another Meta and it will refuse symbols generated with it.
Ok, I tried 21.3+1-6 (-7 wasn't built for ppc it seems) and the problem
is the same. My ISO_Level3_Shift key is sort-of interpreted by emacs as
beeing another Meta and it will refuse symbols generated with it. Dunno
what's wrong, but that basically makes it unuseable. I don't understand
why it does
On Thu, 2005-02-17 at 09:00 +0100, Jérôme Marant wrote:
> Quoting Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
>
>
> > > What exactly is ISO_Level3_Shift?
> >
> > I use it to obtain additional symbols, I map it to the left "Alt" key
> > (w
On Wed, 2005-02-16 at 23:19 +0100, Jérôme Marant wrote:
> When did this bug first show up? We applied a patch recently which
> was related to xkb map. It has not been applied to XEmacs yet.
Hrm... I just reverted to the October version of emacs
(21.3+1-8 instead of 21.3+1-9) and the problem is th
ult to say. I suppose I could be emacs myself without the
patch to confirm that, but I would need some help I suppose, as I've
never been close to trying to build that monster before :)
> > This basically prevents me from typing |,{,} and other things totally
> > useless to a C programmer :)
>
> :-P
>
--
Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Package: emacs21
Version: 21.3+1-9
Severity: important
Hi !
My xkb modifier map looks like:
modifier_map Shift { Shift_L , Shift_R };
modifier_map Lock { Caps_Lock };
modifier_map Control{ Control_L, Control_R };
modifier_map Mod1 { Meta_L, Meta_R };
modifier_map Mod3
55 matches
Mail list logo
