On Thursday, November 8, 2018 8:55:47 AM CET Wang, Dongsheng wrote:
> On 2018/11/8 15:44, Rafael J. Wysocki wrote:
> > On Thursday, November 8, 2018 8:22:16 AM CET Wang Dongsheng wrote:
> >> Add support for parsing the ACPI data node for PHY devices on an MDIO bus.
> >>
On Thursday, November 8, 2018 8:22:16 AM CET Wang Dongsheng wrote:
> Add support for parsing the ACPI data node for PHY devices on an MDIO bus.
> The current implementation depend on mdio bus scan.
> With _DSD device properties we can finally do this:
>
> Device (MDIO) {
> Name (_DSD,
On Tue, Jul 24, 2018 at 6:49 PM, Kees Cook wrote:
> In the quest to remove all stack VLA usage from the kernel[1], this
> removes the discouraged use of AHASH_REQUEST_ON_STACK by switching to
> shash directly and allocating the descriptor in heap memory (which should
> be fine: the tfm has
Hellwig <h...@lst.de>
It is OK AFAICS.
Reviewed-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
On Tue, Jan 23, 2018 at 7:12 AM, Marcin Wojtas wrote:
> Hi Rafael,
>
>> > if (res)
>> > return res;
>> >
>> > - return device_get_mac_addr(dev, "address", addr, alen);
>> > + return fwnode_get_mac_addr(fwnode, "address", addr, alen);
>> > +}
> This commit also introduces a macro, thanks to which it is
> possible to iterate over the available fwnodes, using the
> new function described above.
>
> Signed-off-by: Marcin Wojtas <m...@semihalf.com>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.co
ode_get_mac_address(). This commit also changes
> device_get_mac_address() routine to be its wrapper, in order
> to prevent unnecessary duplication.
>
> Signed-off-by: Marcin Wojtas <m...@semihalf.com>
> Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> ---
&
On Thu, Jan 18, 2018 at 1:31 PM, Marcin Wojtas wrote:
> Until now there were two very similar functions allowing
> to get Linux IRQ number from ACPI handle (acpi_irq_get())
> and OF node (of_irq_get()). The first one appeared to be used
> only as a subroutine of
_mode(). This commit also changes
> device_get_phy_mode() routine to be its wrapper, in order
> to prevent unnecessary duplication.
>
> Signed-off-by: Marcin Wojtas <m...@semihalf.com>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> ---
> drivers/base/propert
On Wednesday, January 3, 2018 11:38:12 AM CET Jonathan McDowell wrote:
> On Wed, Jan 03, 2018 at 11:11:29AM +0900, Joonsoo Kim wrote:
> > On Tue, Jan 02, 2018 at 11:25:01AM +0100, Rafael J. Wysocki wrote:
> > > On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim <iamjoonsoo@
dress(). This commit also changes
> device_get_mac_address() routine to be its wrapper, in order
> to prevent unnecessary duplication.
>
> Signed-off-by: Marcin Wojtas <m...@semihalf.com>
The changes look reasonable to me, so
Acked-by: Rafael J. Wysocki <rafael.j.wyso
On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim wrote:
> On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote:
>> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote:
>> > On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote:
>> > > I've been
On Tuesday, December 26, 2017 3:36:41 AM CET Jeffy Chen wrote:
>
> Currently we are handling wake irq in mrvl wifi driver. Move it into
> pci core.
>
> Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi).
>
>
> Changes in v13:
> Fix compiler error reported by kbuild test robot
t raid6_calls raid6_sse2x2 = {
> raid6_sse22_gen_syndrome,
> @@ -366,9 +366,9 @@ static void raid6_sse24_gen_syndrome(int disks, size_t
> bytes, void **ptrs)
> kernel_fpu_end();
> }
>
> - static void raid6_sse24_xor_syndrome(int disks, int start, int stop,
> +static void raid6_sse24_xor_syndrome(int disks, int start, int stop,
>size_t bytes, void **ptrs)
> - {
> +{
> u8 **dptr = (u8 **)ptrs;
> u8 *p, *q;
> int d, z, z0;
> @@ -471,7 +471,7 @@ static void raid6_sse24_gen_syndrome(int disks, size_t
> bytes, void **ptrs)
> }
> asm volatile("sfence" : : : "memory");
> kernel_fpu_end();
> - }
> +}
>
>
> const struct raid6_calls raid6_sse2x4 = {
> diff --git a/sound/soc/fsl/fsl_dma.c b/sound/soc/fsl/fsl_dma.c
> index 0c11f434a374..ec619f51d336 100644
> --- a/sound/soc/fsl/fsl_dma.c
> +++ b/sound/soc/fsl/fsl_dma.c
> @@ -879,7 +879,7 @@ static const struct snd_pcm_ops fsl_dma_ops = {
> };
>
> static int fsl_soc_dma_probe(struct platform_device *pdev)
> - {
> +{
> struct dma_object *dma;
> struct device_node *np = pdev->dev.of_node;
> struct device_node *ssi_np;
>
> --
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
for the ACPI part.
Thanks!
On 12/18/2017 10:17 AM, Marcin Wojtas wrote:
Hi,
This patchset introduces ACPI support in mvpp2 and mvmdio drivers.
First three patches introduce fwnode helpers for obtaining PHY
information from nodes and also MDIO fwnode API for registering
the bus with its PHY/devices.
Following patches
On Friday, October 27, 2017 9:26:05 AM CEST Jeffy Chen wrote:
>
> Currently we are handling wake irq in mrvl wifi driver. Move it into
> pci core.
>
> Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi).
>
>
> Changes in v10:
> Use device_set_wakeup_capable() instead of
able_group_ops,
> };
>
> -static struct config_item_type acpi_root_group_type = {
> +static const struct config_item_type acpi_root_group_type = {
> .ct_owner = THIS_MODULE,
> };
>
>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
On Thu, Oct 5, 2017 at 10:57 AM, Daniel Drake wrote:
> Hi,
>
> On the Acer laptop models Aspire ES1-533, Aspire ES1-732, PackardBell
> ENTE69AP and Gateway NE533, we are seeing a problem where the system
> immediately wakes up after being put into S3 suspend.
>
> This problem
On Friday, September 1, 2017 1:29:43 AM CEST Kees Cook wrote:
> In several places, .data is checked for initialization to gate early
> calls to del_timer_sync(). Checking for .function is equally valid, so
> switch to this in all callers.
>
> Cc: "Rafael J. Wysocki"
On Monday, August 21, 2017 1:43:07 PM CEST Bhumika Goyal wrote:
> Make these const as they are only passed as an argument to the function
> device_create_file and device_remove_file and the corresponding
> arguments are of type const.
> Done using Coccinelle
>
> Signed-off-by: Bhumika Goyal
On Mon, Aug 21, 2017 at 1:43 PM, Bhumika Goyal wrote:
> Make these const. Done using Coccinelle.
>
> @match disable optional_qualifier@
> identifier s;
> @@
> static struct device_attribute s = {...};
>
> @ref@
> position p;
> identifier match.s;
> @@
> s@p
>
> @good1@
>
On Fri, Feb 17, 2017 at 8:11 AM, Joe Perches wrote:
> There are ~4300 uses of pr_warn and ~250 uses of the older
> pr_warning in the kernel source tree.
>
> Make the use of pr_warn consistent across all kernel files.
>
> This excludes all files in tools/ as there is a separate
>
On Thursday, October 27, 2016 01:53:03 PM Ulf Hansson wrote:
> On 27 October 2016 at 13:41, Geert Uytterhoeven wrote:
> > Hi Ulf,
> >
> > On Thu, Oct 27, 2016 at 1:23 PM, Ulf Hansson wrote:
> >> The smsc911c driver puts its device into low power
On Friday, June 03, 2016 10:55:08 AM Yisen Zhuang wrote:
> From: Kejian Yan
>
> This series adds HNS support of acpi. The routine will call some ACPI
> helper functions, like acpi_dev_found() and acpi_evaluate_dsm(), which
> are not included in other cases. In order to make
acpi_processor_cx * [CPUIDLE_STATE_MAX],
> - acpi_cstate);
> +static
> +DEFINE_PER_CPU(struct acpi_processor_cx * [CPUIDLE_STATE_MAX], acpi_cstate);
>
> static int disabled_by_idle_boot_param(void)
> {
For the above:
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
On Monday, November 09, 2015 08:56:10 PM Tetsuo Handa wrote:
> There are many locations that do
>
> if (memory_was_allocated_by_vmalloc)
> vfree(ptr);
> else
> kfree(ptr);
>
> but kvfree() can handle both kmalloc()ed memory and vmalloc()ed memory
> using is_vmalloc_addr(). Unless
On 10/6/2015 1:08 PM, David Woodhouse wrote:
On Mon, 2015-10-05 at 17:20 -0700, Charles Garcia-Tobin wrote:
it in ACPI circles
unless we had wider agreement among OSs to use it. AFAIK PRP1 has not
actually been approved yet in the specification forum, and that it in
itself is more of a
On Monday, September 28, 2015 10:24:58 AM Arnd Bergmann wrote:
> On Sunday 27 September 2015 16:10:48 Rafael J. Wysocki wrote:
> > On Saturday, September 26, 2015 09:33:56 PM Arnd Bergmann wrote:
> > > On Saturday 26 September 2015 11:40:00 Viresh Kumar wrote:
> > > >
h platforms yet, but the
> code needs to be robust for such a case.
>
> Fix that by changing type of 'global_lock' to u32.
>
> Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Greg, please take this one along wi
On Saturday, September 26, 2015 12:52:08 PM James Bottomley wrote:
> On Fri, 2015-09-25 at 22:58 +0200, Rafael J. Wysocki wrote:
> > On Friday, September 25, 2015 01:25:49 PM Viresh Kumar wrote:
> > > On 25 September 2015 at 13:33, Rafael J. Wysocki <r...@rjwyso
On Saturday, September 26, 2015 09:33:56 PM Arnd Bergmann wrote:
> On Saturday 26 September 2015 11:40:00 Viresh Kumar wrote:
> > On 25 September 2015 at 15:19, Rafael J. Wysocki <raf...@kernel.org> wrote:
> > > So if you allow something like debugfs to update your structur
On Friday, September 25, 2015 01:25:49 PM Viresh Kumar wrote:
> On 25 September 2015 at 13:33, Rafael J. Wysocki <r...@rjwysocki.net> wrote:
> > You're going to change that into bool in the next patch, right?
>
> Yeah.
>
> > So what if bool is a byte and the fiel
; code needs to be robust for such a case.
>
> Fix that by passing a local variable to debugfs_create_bool() and
> assigning its value to global_lock later.
>
> Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
On Friday, September 25, 2015 10:18:13 PM Rafael J. Wysocki wrote:
> On Friday, September 25, 2015 09:41:37 AM Viresh Kumar wrote:
> > global_lock is defined as an unsigned long and accessing only its lower
> > 32 bits from sysfs is incorrect, as we need to consider other 32 b
On Friday, September 25, 2015 11:52:56 AM Viresh Kumar wrote:
> On 25-09-15, 20:49, Johannes Berg wrote:
> > Ok, then, but that means Rafael is completely wrong ...
> > debugfs_create_bool() takes a *pointer* and it needs to be long-lived,
> > it can't be on the stack. You also don't get a call
On Friday, September 25, 2015 10:26:22 PM Rafael J. Wysocki wrote:
> On Friday, September 25, 2015 11:52:56 AM Viresh Kumar wrote:
> > On 25-09-15, 20:49, Johannes Berg wrote:
> > > Ok, then, but that means Rafael is completely wrong ...
> > > debugfs_create_bool() tak
On Fri, Sep 25, 2015 at 11:44 PM, Viresh Kumar <viresh.ku...@linaro.org> wrote:
> On 25-09-15, 22:58, Rafael J. Wysocki wrote:
>> Say you have three adjacent fields in a structure, x, y, z, each one byte
>> long.
>> Initially, all of them are equal to 0.
>>
>&g
On 9/25/2015 5:28 PM, Catalin Marinas wrote:
On Thu, Sep 24, 2015 at 07:10:38PM +0100, David Woodhouse wrote:
On Thu, 2015-09-24 at 16:15 +0100, Catalin Marinas wrote:
With "PRP0001", they can skip the _DSD properties review process (not
that they bother much currently) as long as the existing
On 9/23/2015 8:41 PM, David Woodhouse wrote:
On Wed, 2015-08-12 at 17:06 -0500, Jeremy Linton wrote:
+static const struct acpi_device_id smsc911x_acpi_match[] = {
+ { "ARMH9118", 0 },
+ { }
+};
+MODULE_DEVICE_TABLE(acpi, smsc911x_acpi_match);
+
static struct platform_driver
On Wednesday, August 26, 2015 01:20:44 PM Guenter Roeck wrote:
Return -ENXIO if device property array access functions don't find
a suitable firmware interface.
This lets drivers decide if they should use available platform data
instead.
Cc: Rafael J. Wysocki rafael.j.wyso...@intel.com
On Wednesday, August 26, 2015 04:25:59 PM Guenter Roeck wrote:
On 08/26/2015 04:37 PM, Rafael J. Wysocki wrote:
On Wednesday, August 26, 2015 01:20:44 PM Guenter Roeck wrote:
Return -ENXIO if device property array access functions don't find
a suitable firmware interface.
This lets
Hi Mark,
On Fri, Aug 7, 2015 at 7:51 PM, Mark Rutland mark.rutl...@arm.com wrote:
[Correcting the devicetree list address, which I typo'd in my original
reply]
+static const char * const addr_propnames[] = {
+ mac-address,
+ local-mac-address,
+ address,
+};
If these are going
Hi David,
On Sat, Aug 8, 2015 at 2:11 AM, David Daney dda...@caviumnetworks.com wrote:
On 08/07/2015 05:05 PM, Rafael J. Wysocki wrote:
[cut]
It is actually useful to people as far as I can say.
Also, if somebody is going to use properties with ACPI, why whould
they use a different set
Hi David,
On Fri, Aug 7, 2015 at 8:14 PM, David Daney dda...@caviumnetworks.com wrote:
On 08/07/2015 07:54 AM, Graeme Gregory wrote:
On Thu, Aug 06, 2015 at 05:33:10PM -0700, David Daney wrote:
From: David Daney david.da...@cavium.com
Find out which PHYs belong to which BGX instance in the
On Thursday, August 06, 2015 10:48:48 AM Heikki Krogerus wrote:
On Wed, Aug 05, 2015 at 05:02:18PM +0300, Andy Shevchenko wrote:
On Wed, 2015-08-05 at 16:39 +0300, Heikki Krogerus wrote:
Marcos for easier creation of build-in property entries.
Signed-off-by: Heikki Krogerus
);
+
Well, so is this going to work for PCI too after all?
acpi_physnode_link_name(physical_node_name, node_id);
retval = sysfs_create_link(acpi_dev-dev.kobj, dev-kobj,
physical_node_name);
--
I speak only for myself.
Rafael J. Wysocki, Intel Open
On Friday, May 22, 2015 07:15:17 PM Suravee Suthikulanit wrote:
On 5/22/2015 6:05 PM, Rafael J. Wysocki wrote:
On Friday, May 22, 2015 05:24:15 PM Suravee Suthikulanit wrote:
Not sure if this went out earlier. So I am resending.
On 5/22/15 16:56, Rafael J. Wysocki wrote:
diff --git
On Friday, May 22, 2015 05:24:15 PM Suravee Suthikulanit wrote:
Not sure if this went out earlier. So I am resending.
On 5/22/15 16:56, Rafael J. Wysocki wrote:
diff --git a/drivers/acpi/glue.c b/drivers/acpi/glue.c
index 39c485b..b9657af 100644
--- a/drivers/acpi/glue.c
+++ b/drivers
On Monday, May 18, 2015 05:38:17 PM Suravee Suthikulanit wrote:
Hi Rafael,
On 5/15/2015 6:53 PM, Rafael J. Wysocki wrote:
On Friday, May 15, 2015 04:23:09 PM Suravee Suthikulpanit wrote:
[...]
diff --git a/drivers/acpi/acpi_platform.c b/drivers/acpi/acpi_platform.c
index 4bf7559
On Monday, 18 of February 2008, Pierre Ossman wrote:
The patch [RTNETLINK]: Send a single notification on device state changes.
kills (at least)
the keyboard here. Everything seems to work fine in single user mode, but
when init starts
spawning of logins, the keyboard goes bye-bye. Even the
On Monday, 18 of February 2008, Jiri Kosina wrote:
This reverts commit 45b503548210fe6f23e92b856421c2a3f05fd034.
It contains deadlock, and breaks userspace applications (wpa_supplicant,
networkmanager). References:
http://bugzilla.kernel.org/show_bug.cgi?id=10002
On Sunday, 13 of January 2008, Andrew Morton wrote:
2.6.23 also has this warning in sky2_err_intr() but it doesn't trigger
there. Rafael, I think we'd have to class this as a post-2.6.23
regression.
Yes, it's been being tracked already.
--
To unsubscribe from this list: send the line
I wonder if commit 84cd2dfb04d23a961c5f537baa243fa54d0987ac
sky2: remove check for PCI wakeup setting from BIOS has anything to do with
it, btw.
supersud501, can you please check if the bug is still present in the current
Linus' tree?
--
To unsubscribe from this list: send the line unsubscribe
http://bugzilla.kernel.org/show_bug.cgi?id=9721
On Saturday, 12 of January 2008, supersud501 wrote:
I'll do the git-bisect (just downloading linux-2.6.git), but i forgot to
mention one little thing: i'm using x64 version of kernel - does this
play an important role?
No, it doesn't.
--
To
http://bugzilla.kernel.org/show_bug.cgi?id=9721
On Friday, 11 of January 2008, supersud501 wrote:
Stephen Hemminger wrote:
On Wed, 9 Jan 2008 16:03:00 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web
On Friday, 11 of January 2008, supersud501 wrote:
Rafael J. Wysocki wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9721
allright, didn't see that before, sorry, here are the results:
kernel 2.6.23.12 acpi=off: when shutting down the system doesn't
poweroff (of course), but pressing
On Tuesday, 8 of January 2008, Linus Torvalds wrote:
On Tue, 8 Jan 2008, Arjan van de Ven wrote:
ok done; I had to fizzle a bit because some things aren't *exactly* a
BUG() statement but I track them anyway (things like the sleeping in
invalid context check), so I had to somewhat
On Sunday, 16 of December 2007, Bernard Pidoux wrote:
With 2.6.24-rc5 there is no /proc/net/ax25
FYI, I've created a Bugzilla entry for this issue at:
http://bugzilla.kernel.org/show_bug.cgi?id=9589
Please add your address to the CC list in there.
Thanks,
Rafael
Here is an extract from
On Friday, 14 of December 2007, Ray Lee wrote:
tshark -i eth0, eth1, lo are all empty. Works under 2.6.23.0 just
fine. A quick scan of the log between 2.6.24-rc3 and current tip
(-rc5) doesn't show any obvious fixes, but then again, what do I know.
I'll check current tip on the weekend when
On Wednesday, 21 of November 2007, Roland McGrath wrote:
can you see any danger to providing a /proc/self_task/ link? (or can you
think of a better name/API/approach)
That is a poor name to choose given /proc/self/task exists as something
else (just try writing a sentence comparing them
On Monday, 19 of November 2007, Pavel Machek wrote:
Hi!
I think that this worked before:
[EMAIL PROTECTED]:/proc# find . -name timer_info
find: WARNING: Hard link count is wrong for ./net: this may be a bug
in your filesystem driver. Automatically turning on find's -noleaf
option.
On Tuesday, 13 of November 2007, Mark Lord wrote:
Matthew Wilcox wrote:
On Tue, Nov 13, 2007 at 01:43:53PM -0500, Mark Lord wrote:
mkdir t
cd t
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
(wait half an hour)
/usr/bin/du -s linux-2.6
522732
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 01:06:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Monday, 5 of November 2007, Grant Wilson wrote:
Hi,
I got this oops on 2.6.24-rc1-641-gb4f5550:
(1) Is this reproducible?
(2) Did it happen
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 16:53:10 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 01:06:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Monday, 5
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 22:42:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 16:53:10 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 8
On Friday, 15 June 2007 23:50, David Greaves wrote:
I've started a new thread here since the old one got somewhat hijacked.
Rafael J. Wysocki wrote:
On Friday, 1 June 2007 23:23, David Greaves wrote:
Not a regression though, it does it in 2.6.21
If I cause the system to save state
On Tuesday, 5 June 2007 07:56, Stephen Hemminger wrote:
I hope soon to add suspend/resume to the network device class
and remove driver specific suspend/resume from lots of devices.
The class suspend routine would just be:
pci_save_state
dev-stop
resume is
Hi,
On Monday, 4 June 2007 13:11, Pavel Machek wrote:
Hi!
From: Rafael J. Wysocki [EMAIL PROTECTED]
Add suspend/resume support to the uli526x network driver (tested on x86_64,
with 'Ethernet controller: ALi Corporation M5263 Ethernet Controller, rev
40').
Signed-off-by: Rafael
Hi,
On Monday, 4 June 2007 23:16, Nigel Cunningham wrote:
Hi.
On Mon, 2007-06-04 at 15:49 +0200, Rafael J. Wysocki wrote:
On Monday, 4 June 2007 13:11, Pavel Machek wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
Add suspend/resume support to the uli526x network driver (tested
From: Rafael J. Wysocki [EMAIL PROTECTED]
Add suspend/resume support to the uli526x network driver (tested on x86_64,
with 'Ethernet controller: ALi Corporation M5263 Ethernet Controller, rev 40').
Signed-off-by: Rafael J. Wysocki [EMAIL PROTECTED]
drivers/net/tulip/uli526x.c | 120
Hi,
The uli526x network driver doesn't implement .suspend and .resume methods
and the interface handled by it is unuseable after the resume. Since I have
one of these boards in a box which is used to test the suspend/resume
functionality, I've prepared the appended patch that adds the .suspend
On Friday, 9 February 2007 17:53, Michael Buesch wrote:
On Friday 09 February 2007 17:18, Larry Finger wrote:
After a suspend/resume cycle, bcm43xx-softmac has lost its association with
the AP and requires manual intervention. This situation is fixed by making
one of softmac's internal
On Tuesday, 23 January 2007 21:26, Larry Finger wrote:
The bcm43xx scales the rate information supplied to a WE iwlist rate call
incorrectly.
Signed-off-by: Larry Finger [EMAIL PROTECTED]
---
John,
This fix should be applied to wireless-2.6. As it is a bug fix, it could also
be sent
Hi,
On Friday, 22 December 2006 18:30, Larry Finger wrote:
I'm trying to make the bcm43xx driver out of the 2.6.20-rc1-mm1 kernel work on
an HPC nx6325, with no luck, so far, although I'm using a firmware that has
been reported to work with these boxes
On Tuesday, 5 December 2006 23:07, Auke Kok wrote:
[resend]
Quick note: I loaded up 2.6.19-rc6-mm2 on a platform here and noticed that
the onboard
e1000 NIC was enumerated to eth1 instead of eth0. on 2.6.18.5 and any other
kernel I
used before, it was properly named eth0 after startup.
On Friday, 1 December 2006 02:20, Greg KH wrote:
On Wed, Nov 29, 2006 at 06:18:09PM -0800, Andrew Morton wrote:
On Thu, 30 Nov 2006 02:04:15 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
git-netdev-all.patch
git-netdev-all-fixup.patch
libphy-dont-do-that.patch
On Thursday, 30 November 2006 02:04, Rafael J. Wysocki wrote:
On Thursday, 30 November 2006 00:26, Andrew Morton wrote:
On Thu, 30 Nov 2006 00:08:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Wednesday, 29 November 2006 22:31, Rafael J. Wysocki wrote:
On Wednesday, 29
[Trimmed the Cc list a bit.]
On Thursday, 30 November 2006 22:12, Andrew Morton wrote:
On Thu, 30 Nov 2006 21:21:27 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 30 November 2006 02:04, Rafael J. Wysocki wrote:
On Thursday, 30 November 2006 00:26, Andrew Morton wrote
On Thursday, 30 November 2006 22:32, Rafael J. Wysocki wrote:
[Trimmed the Cc list a bit.]
On Thursday, 30 November 2006 22:12, Andrew Morton wrote:
On Thu, 30 Nov 2006 21:21:27 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 30 November 2006 02:04, Rafael J. Wysocki
On Wednesday, 29 November 2006 22:30, Andrew Morton wrote:
On Wed, 29 Nov 2006 21:08:00 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Wednesday, 29 November 2006 20:54, Rafael J. Wysocki wrote:
On Tuesday, 28 November 2006 11:02, Andrew Morton wrote:
Temporarily
On Wednesday, 29 November 2006 22:31, Rafael J. Wysocki wrote:
On Wednesday, 29 November 2006 22:30, Andrew Morton wrote:
On Wed, 29 Nov 2006 21:08:00 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Wednesday, 29 November 2006 20:54, Rafael J. Wysocki wrote:
On Tuesday, 28
On Thursday, 30 November 2006 00:26, Andrew Morton wrote:
On Thu, 30 Nov 2006 00:08:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Wednesday, 29 November 2006 22:31, Rafael J. Wysocki wrote:
On Wednesday, 29 November 2006 22:30, Andrew Morton wrote:
On Wed, 29 Nov 2006 21:08
On Monday, 23 October 2006 09:47, Christian stahl wrote:
After upgrading from 2.6.16.20 to 2.6.18.1 my Siemens Scenic
Mobile 750AGP Notebook hangs after resuming from suspend.
However resuming from suspend works properly if:
- the prism 2.5 WLAN card is removed before suspending
- the
On Saturday, 21 October 2006 19:02, Andrew Morton wrote:
cc's added.
On Sat, 21 Oct 2006 15:22:39 +0200
Norbert Preining [EMAIL PROTECTED] wrote:
Hi all!
I get the same bug again and again, always when ifplugd is started:
tg3: eth0: No firmware running.
BUG: soft lockup
On Saturday, 23 September 2006 08:03, Ray Lee wrote:
On 9/22/06, Larry Finger [EMAIL PROTECTED] wrote:
When we found the cause of NETDEV watchdog timeouts in the wireless-2.6
code,
I knew that the 2.6.18 release code would cause a serious regression.
I don't know if this is the lockup
On Wednesday, 20 September 2006 16:23, Mike Galbraith wrote:
On Tue, 2006-09-19 at 13:36 -0700, Andrew Morton wrote:
On Tue, 19 Sep 2006 22:25:21 +0200
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
- It took maybe ten hours solid work to get this dogpile vaguely
compiling
On Tuesday, 19 September 2006 22:36, Andrew Morton wrote:
On Tue, 19 Sep 2006 22:25:21 +0200
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
- It took maybe ten hours solid work to get this dogpile vaguely
compiling and limping to a login prompt on x86, x86_64 and powerpc.
I guess
On Tuesday, 19 September 2006 23:30, Rafael J. Wysocki wrote:
On Tuesday, 19 September 2006 22:36, Andrew Morton wrote:
On Tue, 19 Sep 2006 22:25:21 +0200
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
- It took maybe ten hours solid work to get this dogpile vaguely
compiling
On Wednesday, 20 September 2006 00:30, Greg KH wrote:
On Tue, Sep 19, 2006 at 03:06:29PM -0700, David Miller wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
Date: Wed, 20 Sep 2006 00:06:52 +0200
I _guess_ the problem is caused by
gregkh-driver-network-class_device-to-device.patch
On Tuesday 15 August 2006 01:01, Laurent Riffard wrote:
Le 14.08.2006 23:25, Rafael J. Wysocki a écrit :
On Monday 14 August 2006 22:06, Laurent Riffard wrote:
Le 14.08.2006 19:47, Laurent Riffard a écrit :
Le 14.08.2006 18:50, Andrew Morton a écrit :
On Mon, 14 Aug 2006 16:38:47 +0200
On Tuesday 15 August 2006 17:38, Laurent Riffard wrote:
Le 15.08.2006 12:10, Rafael J. Wysocki a écrit :
On Tuesday 15 August 2006 01:01, Laurent Riffard wrote:
Le 14.08.2006 23:25, Rafael J. Wysocki a écrit :
On Monday 14 August 2006 22:06, Laurent Riffard wrote:
Le 14.08.2006 19:47
On Monday 14 August 2006 22:06, Laurent Riffard wrote:
Le 14.08.2006 19:47, Laurent Riffard a écrit :
Le 14.08.2006 18:50, Andrew Morton a écrit :
On Mon, 14 Aug 2006 16:38:47 +0200
Laurent Riffard [EMAIL PROTECTED] wrote:
Le 13.08.2006 10:24, Andrew Morton a __crit :
On Saturday 12 August 2006 15:39, Jeff Garzik wrote:
Andrew Morton wrote:
It would be good if you could poke around in gdb, work out exactly which
statement it's oopsing at, please.
I'm also interested to know if the problem goes away when you disable
preempt...
That will take some time
Hi,
On 2.6.18-rc3-mm2 with hotfixes I get things like the appended one on attempts
to suspend to disk. It occurs while devices are being suspended and is fairly
reproducible.
Greetings,
Rafael
Suspending device :01:00.0
Suspending device :02:02.0
Suspending device :02:01.4
On Saturday 12 August 2006 14:28, Andrew Morton wrote:
On Sat, 12 Aug 2006 12:07:42 +0200
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Hi,
On 2.6.18-rc3-mm2 with hotfixes I get things like the appended one on
attempts
to suspend to disk. It occurs while devices are being suspended
On Saturday 12 August 2006 18:12, Edgar E. Iglesias wrote:
On Sat, Aug 12, 2006 at 04:31:18PM +0200, Rafael J. Wysocki wrote:
On Saturday 12 August 2006 14:28, Andrew Morton wrote:
On Sat, 12 Aug 2006 12:07:42 +0200
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Hi,
On 2.6.18
On Saturday 12 August 2006 16:32, Rafael J. Wysocki wrote:
On Saturday 12 August 2006 15:39, Jeff Garzik wrote:
Andrew Morton wrote:
It would be good if you could poke around in gdb, work out exactly which
statement it's oopsing at, please.
I'm also interested to know if the problem
On Saturday 12 August 2006 20:16, Edgar E. Iglesias wrote:
On Sat, Aug 12, 2006 at 07:13:01PM +0200, Rafael J. Wysocki wrote:
Apparently it doesn't.
Hi, could you try and see if this helps?
With the patch I can't reproduce the problem. I sometimes get the error
messages from the interrupt
On Friday 09 June 2006 03:56, Jeremy Fitzhardinge wrote:
Rafael J. Wysocki wrote:
Please try doing echo 8 /proc/sys/kernel/printk before suspend.
Um, why? That would increase the amount of log output, but I don't see
how it would help with netconsole preventing suspend, or not being
On Thursday 08 June 2006 19:50, Jeremy Fitzhardinge wrote:
I've been trying to get suspend/resume working well on my new laptop.
In general, netconsole has been pretty useful for extracting oopses and
other messages, but it is of more limited help in debugging the actual
suspend/resume
100 matches
Mail list logo