On Tue, Jan 15, 2013 at 10:21:53PM -0800, russell wrote:
> On 01/17/2013 09:46 PM, Philip Guenther wrote:
> >I've had this exact diff, same whitespace and all, floating in my tree
> >since Aug 2011.
> >
> >ok guenther@
> >
> silly minutia, but it was not as easy to figure out as I would have
> exp
On 2013/01/18 13:35, Christian Weisgerber wrote:
> Claudio Jeker wrote:
>
> > Here is a diff to support the newer Broadcom chips seen in Dell and HP
> > servers. This was tested against a BCM57765, BCM5721, and BCM5720.
> > This needs a lot of testing on ANY bge(4).
>
> I already told claudio@ a
Claudio Jeker wrote:
> Here is a diff to support the newer Broadcom chips seen in Dell and HP
> servers. This was tested against a BCM57765, BCM5721, and BCM5720.
> This needs a lot of testing on ANY bge(4).
I already told claudio@ and dlg@, but for the public record:
With this diff my BCM5761 n
On Fri, Jan 18, 2013 at 02:00:19PM +0100, Martin Pieuchot wrote:
> If I understand correctly, actually once you've started X you can't see
> the console anymore, even if you kill X, right?
Yes. The console works fine until X is started for the first time.
I got some hints from Alex Deucher about
On 06/01/13(Sun) 16:42, Stefan Sperling wrote:
> I have the following radeon chipset in a thinkpad x130e notebook:
>
> [ 643.577] (--) RADEON(0): Chipset: "AMD Radeon HD 6300 Series Graphics"
> (ChipID = 0x9806)
>
> In the driver this is called a "PALM" generation chip. The radeon driver
> con
On 01/17/2013 09:46 PM, Philip Guenther wrote:
I've had this exact diff, same whitespace and all, floating in my tree
since Aug 2011.
ok guenther@
silly minutia, but it was not as easy to figure out as I would have
expected.
had to look it up in fcntl.h like some sort of barbarian
--- open.2
