On Apr 23, 2013, at 4:33 AM, Steven Hartland wrote:
>>>
>>> If we can't reach an agreement, I'm happy to wrap the relevant bits with
>>> an "if (bootverbose)", but I really feel users should have some way to
>>> see this information outside of bootverbose.
>> Both da and ada drivers already hav
Your meta-commentary here is irritating.
They're called "quirks" because that is the named given to them in CAM>
Scott
On Apr 23, 2013, at 9:33 AM, Adrian Chadd wrote:
> .. are we really debating this?
>
> Stop calling them quirks. That sounds like something that won't mess
> up your actual r
On Wed, 2013-04-24 at 11:59 -0700, Adrian Chadd wrote:
> I think this just outlines the problem - bootverbose is too verbose.
>
> eg, what the audio code outputs. And yes, net80211 when you're doing 11n.
>
I agree that the sound driver(s) output Too Much Stuff with bootverbose,
so much so that i
I think this just outlines the problem - bootverbose is too verbose.
eg, what the audio code outputs. And yes, net80211 when you're doing 11n.
Adrian
On 23 April 2013 23:15, Matthias Andree wrote:
> Am 23.04.2013 09:44, schrieb Alexander Motin:
>
>> Let me disagree. bootverbose keeps dmesg r
Am 23.04.2013 09:44, schrieb Alexander Motin:
> Let me disagree. bootverbose keeps dmesg readable for average user,
> while quirks are specific driver workarounds and their names may confuse
> more then really help. If every driver print its quirks, dmesg would be
> two times bigger. There is boot
> I've written the following patches and done the following testing (see
> the results.*.txt files):
>
> http://jdc.koitsu.org/freebsd/quirk_printing/
>
> Important: these are against stable/9 r249715.
>
> Folks are welcome to try these; I've tested about as best as I can.
>
> Questions/comment
W dniu 2013-04-23 18:33, Adrian Chadd pisze:
> .. are we really debating this?
>
> Stop calling them quirks. That sounds like something that won't mess
> up your actual runtime. It's not giving them enough "weight". They're
> more "device behaviours" or "device flags" or something. Print them
> o
.. are we really debating this?
Stop calling them quirks. That sounds like something that won't mess
up your actual runtime. It's not giving them enough "weight". They're
more "device behaviours" or "device flags" or something. Print them
out like that. I think that _not_ printing them out at boot
On Tue, Apr 23, 2013 at 02:15:31PM +0100, Tom Evans wrote:
> On Tue, Apr 23, 2013 at 1:51 PM, Jeremy Chadwick wrote:
> > On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote:
> >> >4) camcontrol wouldn't address the need/interest for ahci(4) quirks to
> >> >be made available.
> >>
> >>
On 4/23/2013 8:15 AM, Tom Evans wrote:
On Tue, Apr 23, 2013 at 1:51 PM, Jeremy Chadwick wrote:
On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote:
4) camcontrol wouldn't address the need/interest for ahci(4) quirks to
be made available.
Why?
Because camcontrol is for CAM. ahc
On Tue, 23 Apr 2013 05:15:06 -0700, Jeremy Chadwick wrote:
> On Tue, Apr 23, 2013 at 01:55:15PM +0300, Alexander Motin wrote:
> > Virtual machine?
>
> Depends on the kind of VM. The ones I've used (VMware Workstation,
> VirtualBox, and KQemu) emulate some hardware -- usually for storage,
> using
On Tue, Apr 23, 2013 at 1:51 PM, Jeremy Chadwick wrote:
> On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote:
>> >4) camcontrol wouldn't address the need/interest for ahci(4) quirks to
>> >be made available.
>>
>> Why?
>
> Because camcontrol is for CAM. ahci(4) is not part of CAM. T
On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote:
> - Original Message - From: "Jeremy Chadwick"
>
> >>Wouldn't camcontrol be a better place for this?
> >
> >1) Not possible at this time -- the ADA_Q_* quirks are not exported to
> >userland (i.e. /usr/include), only the kern
- Original Message -
From: "Jeremy Chadwick"
Wouldn't camcontrol be a better place for this?
1) Not possible at this time -- the ADA_Q_* quirks are not exported to
userland (i.e. /usr/include), only the kernel. camcontrol's source only
relies on things in userland.
Thats not an issu
On Tue, Apr 23, 2013 at 01:55:15PM +0300, Alexander Motin wrote:
> On 23.04.2013 13:49, Jeremy Chadwick wrote:
> >On Tue, Apr 23, 2013 at 12:29:10PM +0300, Alexander Motin wrote:
> >>On 23.04.2013 12:26, Jeremy Chadwick wrote:
> >>>On Tue, Apr 23, 2013 at 10:44:57AM +0300, Alexander Motin wrote:
>
On Tue, Apr 23, 2013 at 12:33:09PM +0100, Steven Hartland wrote:
>
> - Original Message - From: "Alexander Motin"
>
> To: "Jeremy Chadwick"
> Cc: "Kenneth Merry" ;
> Sent: Tuesday, April 23, 2013 10:29 AM
> Subject: Re: ada(4) and
- Original Message -
From: "Alexander Motin"
To: "Jeremy Chadwick"
Cc: "Kenneth Merry" ;
Sent: Tuesday, April 23, 2013 10:29 AM
Subject: Re: ada(4) and ahci(4) quirk printing
On 23.04.2013 12:26, Jeremy Chadwick wrote:
On Tue, Apr 23, 2013 at 10:
On 23.04.2013 13:49, Jeremy Chadwick wrote:
On Tue, Apr 23, 2013 at 12:29:10PM +0300, Alexander Motin wrote:
On 23.04.2013 12:26, Jeremy Chadwick wrote:
On Tue, Apr 23, 2013 at 10:44:57AM +0300, Alexander Motin wrote:
On 22.04.2013 08:14, Jeremy Chadwick wrote:
I've written the following patc
On Tue, Apr 23, 2013 at 12:29:10PM +0300, Alexander Motin wrote:
> On 23.04.2013 12:26, Jeremy Chadwick wrote:
> >On Tue, Apr 23, 2013 at 10:44:57AM +0300, Alexander Motin wrote:
> >>On 22.04.2013 08:14, Jeremy Chadwick wrote:
> >>>I've written the following patches and done the following testing (
On 23.04.2013 12:26, Jeremy Chadwick wrote:
On Tue, Apr 23, 2013 at 10:44:57AM +0300, Alexander Motin wrote:
On 22.04.2013 08:14, Jeremy Chadwick wrote:
I've written the following patches and done the following testing (see
the results.*.txt files):
http://jdc.koitsu.org/freebsd/quirk_printing
On Tue, Apr 23, 2013 at 10:44:57AM +0300, Alexander Motin wrote:
> On 22.04.2013 08:14, Jeremy Chadwick wrote:
> >I've written the following patches and done the following testing (see
> >the results.*.txt files):
> >
> >http://jdc.koitsu.org/freebsd/quirk_printing/
> >
> >Important: these are agai
On 22.04.2013 08:14, Jeremy Chadwick wrote:
I've written the following patches and done the following testing (see
the results.*.txt files):
http://jdc.koitsu.org/freebsd/quirk_printing/
Important: these are against stable/9 r249715.
Folks are welcome to try these; I've tested about as best as
22 matches
Mail list logo
