On Monday 13 August 2007, Bjorn Helgaas wrote:
> On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote:
> > This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable
> > PnP by default; it is apparently enabled now and fails to activte IrDA
> > completely. So it moves to
On Monday 13 August 2007, Bjorn Helgaas wrote:
On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote:
This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable
PnP by default; it is apparently enabled now and fails to activte IrDA
completely. So it moves to
On Mon, Aug 13, 2007 at 10:09:46AM -0600, Bjorn Helgaas wrote:
> > [ 2207.986873] smsc_ircc_present: can't get sir_base of 0x2e8
>
> As of 2.6.23-rc2, we should have:
> - probes for 8250 legacy devices (as in 2.6.21 and previous)
> - smsc PNP probes turned off by default (2.6.21 and previous
On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote:
> This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable PnP
> by default; it is apparently enabled now and fails to activte IrDA
> completely. So it moves to post-2.6.22 regressions :)
>
> let me know which
On Saturday 11 August 2007 12:39:35 pm Andrey Borzenkov wrote:
This stopped working again in 2.6.23-rc. In 2.6.22 we decided to disable PnP
by default; it is apparently enabled now and fails to activte IrDA
completely. So it moves to post-2.6.22 regressions :)
let me know which information
On Mon, Aug 13, 2007 at 10:09:46AM -0600, Bjorn Helgaas wrote:
[ 2207.986873] smsc_ircc_present: can't get sir_base of 0x2e8
As of 2.6.23-rc2, we should have:
- probes for 8250 legacy devices (as in 2.6.21 and previous)
- smsc PNP probes turned off by default (2.6.21 and previous had
On Saturday 30 June 2007, Bjorn Helgaas wrote:
> On Saturday 30 June 2007 01:16:18 am Andrey Borzenkov wrote:
> > > This patch fixes the 2.6.22 regression:
> > > "no irda0 interface (2.6.21 was OK), smsc does not find chip"
> >
> > does not work, sorry.
>
> Sigh ;-) Thanks for your patience
On Saturday 30 June 2007, Bjorn Helgaas wrote:
On Saturday 30 June 2007 01:16:18 am Andrey Borzenkov wrote:
This patch fixes the 2.6.22 regression:
no irda0 interface (2.6.21 was OK), smsc does not find chip
does not work, sorry.
Sigh ;-) Thanks for your patience in dealing with
Andrew, can you apply the patch below for 2.6.22? It reverts
smsc-ircc2 to the old blind probing behavior. There's a lot of
infrastructure work I need to do before the PNP probe will be
reliable.
Thanks,
Bjorn
On Sunday 01 July 2007 01:08:16 am Andrey Borzenkov wrote:
> Bjorn Helgaas wrote:
Bjorn Helgaas wrote:
[...]
>
> I suspect that things will mostly work if you load the drivers in
> the (smsc-ircc2, wlags49_h1_cs) order.
yes
> Then smsc-ircc2 has a chance
> to reserve the resources before yenta and wlags49 get involved. But
> of course, we can't rely on that workaround.
>
Bjorn Helgaas wrote:
[...]
I suspect that things will mostly work if you load the drivers in
the (smsc-ircc2, wlags49_h1_cs) order.
yes
Then smsc-ircc2 has a chance
to reserve the resources before yenta and wlags49 get involved. But
of course, we can't rely on that workaround.
yes
Andrew, can you apply the patch below for 2.6.22? It reverts
smsc-ircc2 to the old blind probing behavior. There's a lot of
infrastructure work I need to do before the PNP probe will be
reliable.
Thanks,
Bjorn
On Sunday 01 July 2007 01:08:16 am Andrey Borzenkov wrote:
Bjorn Helgaas wrote:
On Saturday 30 June 2007 03:13:24 pm Andrey Borzenkov wrote:
> After some digging, it works now :) So the story:
>
> PCMCIA includes code for checking for free IO range(s)
> code is active only if CONFIG_ISA is defined
> CONFIG_ISA has this excellent help text:
> Find out whether you
Michal Piotrowski pisze:
> Hi,
>
> Bjorn Helgaas pisze:
>> [patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
>>
>> When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
>> the device is working, but it really isn't configured correctly. The BIOS
>>
Hi,
Bjorn Helgaas pisze:
> [patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
>
> When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
> the device is working, but it really isn't configured correctly. The BIOS
> *will* configure it, but only if we
On Saturday 30 June 2007, Andrey Borzenkov wrote:
> On Saturday 30 June 2007, Bjorn Helgaas wrote:
> > This means that the SMCf010 device *did* respond, I think at the
> > FIR address 0x100. (I can't figure out the "right" way to print
> > those resource_size_t things, so I added some casts in
On Saturday 30 June 2007, Bjorn Helgaas wrote:
> This means that the SMCf010 device *did* respond, I think at the
> FIR address 0x100. (I can't figure out the "right" way to print
> those resource_size_t things, so I added some casts in the appended
> patch.)
>
Those can be 64 bit if
On Saturday 30 June 2007 01:16:18 am Andrey Borzenkov wrote:
> > This patch fixes the 2.6.22 regression:
> > "no irda0 interface (2.6.21 was OK), smsc does not find chip"
>
> does not work, sorry.
Sigh ;-) Thanks for your patience in dealing with this.
> [ 958.125710] 00:0a: SMCf010 not
On Saturday 30 June 2007, Bjorn Helgaas wrote:
> [patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
>
> When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
> the device is working, but it really isn't configured correctly. The BIOS
> *will* configure
On Saturday 30 June 2007, Bjorn Helgaas wrote:
[patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
the device is working, but it really isn't configured correctly. The BIOS
*will* configure it, but
On Saturday 30 June 2007 01:16:18 am Andrey Borzenkov wrote:
This patch fixes the 2.6.22 regression:
no irda0 interface (2.6.21 was OK), smsc does not find chip
does not work, sorry.
Sigh ;-) Thanks for your patience in dealing with this.
[ 958.125710] 00:0a: SMCf010 not
On Saturday 30 June 2007, Bjorn Helgaas wrote:
This means that the SMCf010 device *did* respond, I think at the
FIR address 0x100. (I can't figure out the right way to print
those resource_size_t things, so I added some casts in the appended
patch.)
Those can be 64 bit if
On Saturday 30 June 2007, Andrey Borzenkov wrote:
On Saturday 30 June 2007, Bjorn Helgaas wrote:
This means that the SMCf010 device *did* respond, I think at the
FIR address 0x100. (I can't figure out the right way to print
those resource_size_t things, so I added some casts in the
Hi,
Bjorn Helgaas pisze:
[patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
the device is working, but it really isn't configured correctly. The BIOS
*will* configure it, but only if we call
Michal Piotrowski pisze:
Hi,
Bjorn Helgaas pisze:
[patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
the device is working, but it really isn't configured correctly. The BIOS
*will* configure
On Saturday 30 June 2007 03:13:24 pm Andrey Borzenkov wrote:
After some digging, it works now :) So the story:
PCMCIA includes code for checking for free IO range(s)
code is active only if CONFIG_ISA is defined
CONFIG_ISA has this excellent help text:
Find out whether you have ISA
[patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
the device is working, but it really isn't configured correctly. The BIOS
*will* configure it, but only if we call _SRS after (1) reversing the order
[patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
the device is working, but it really isn't configured correctly. The BIOS
*will* configure it, but only if we call _SRS after (1) reversing the order
Andrey,
Can you try the following patch? It applies on top of the previous
two patches, and it is enough to make the driver find the device on
my Portege 4000. Unfortunately, I can't tell whether it really works
because I don't have a clue about how to make two IR devices talk
to each other.
Andrey,
Can you try the following patch? It applies on top of the previous
two patches, and it is enough to make the driver find the device on
my Portege 4000. Unfortunately, I can't tell whether it really works
because I don't have a clue about how to make two IR devices talk
to each other.
On Saturday 16 June 2007 10:38:56 am Andrey Borzenkov wrote:
> it appears that quirk is not even applied because PnP tells us device is not
> active:
>
> [ 571.118483] pnp: PnP ACPI init
> [ 571.118611] ACPI: bus type pnp registered
> [ 571.158828] quirk_smc_enable: active = 0
> [
On Saturday 16 June 2007 10:38:56 am Andrey Borzenkov wrote:
it appears that quirk is not even applied because PnP tells us device is not
active:
[ 571.118483] pnp: PnP ACPI init
[ 571.118611] ACPI: bus type pnp registered
[ 571.158828] quirk_smc_enable: active = 0
[ 571.182090] pnp:
On Friday 15 June 2007, Bjorn Helgaas wrote:
> On Friday 15 June 2007 07:44:41 am Andrey Borzenkov wrote:
> > On Friday 15 June 2007, Bjorn Helgaas wrote:
> > > Hi Andrey,
> > >
> > > If you have a chance, can you try the attached two patches? The
> > > smsc-preconfig patch makes the HP nx5000
On Friday 15 June 2007, Bjorn Helgaas wrote:
On Friday 15 June 2007 07:44:41 am Andrey Borzenkov wrote:
On Friday 15 June 2007, Bjorn Helgaas wrote:
Hi Andrey,
If you have a chance, can you try the attached two patches? The
smsc-preconfig patch makes the HP nx5000 work, and the
On Friday 15 June 2007 07:44:41 am Andrey Borzenkov wrote:
> On Friday 15 June 2007, Bjorn Helgaas wrote:
> > Hi Andrey,
> >
> > If you have a chance, can you try the attached two patches? The
> > smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
> > patch makes the nw8000/nc8000
On Friday 15 June 2007, Bjorn Helgaas wrote:
> Hi Andrey,
>
> If you have a chance, can you try the attached two patches? The
> smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
> patch makes the nw8000/nc8000 work, too.
>
> I've heard rumors that Windows does basically the same
On Friday 15 June 2007, Bjorn Helgaas wrote:
Hi Andrey,
If you have a chance, can you try the attached two patches? The
smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
patch makes the nw8000/nc8000 work, too.
I've heard rumors that Windows does basically the same thing as
On Friday 15 June 2007 07:44:41 am Andrey Borzenkov wrote:
On Friday 15 June 2007, Bjorn Helgaas wrote:
Hi Andrey,
If you have a chance, can you try the attached two patches? The
smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
patch makes the nw8000/nc8000 work, too.
Hi Andrey,
If you have a chance, can you try the attached two patches? The
smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
patch makes the nw8000/nc8000 work, too.
I've heard rumors that Windows does basically the same thing as the
smsc-quirk patch, so I think there's a chance
Hi Andrey,
If you have a chance, can you try the attached two patches? The
smsc-preconfig patch makes the HP nx5000 work, and the smsc-quirk
patch makes the nw8000/nc8000 work, too.
I've heard rumors that Windows does basically the same thing as the
smsc-quirk patch, so I think there's a chance
On Monday 11 June 2007, Bjorn Helgaas wrote:
> > {pts/1}% lspnp -vv 00:0a
> > 00:0a SMCf010 SMC Fast Infrared Port
> > state = active
> > allocated resources:
> > io 0x100-0x107
> > ...
> >
> > {pts/1}% cat /proc/ioports
> > ...
> > 0100-013f : pcmcia_socket0
> > ...
> >
> >
On Monday 11 June 2007, Bjorn Helgaas wrote:
{pts/1}% lspnp -vv 00:0a
00:0a SMCf010 SMC Fast Infrared Port
state = active
allocated resources:
io 0x100-0x107
...
{pts/1}% cat /proc/ioports
...
0100-013f : pcmcia_socket0
...
{pts/1}% sudo cat
On Sunday 10 June 2007 12:47:07 am Andrey Borzenkov wrote:
> > Maybe we should also run the legacy probe when the PnP one fails. I
> > don't know how the preconfiguration stuff will behave with the device
> > being PnP enabled, but with your patch Andrey will still need to
> > modprobe smsc-ircc
On Sunday 10 June 2007 02:03:03 am Andrey Borzenkov wrote:
> > Can you set CONFIG_ACPI_DEBUG=y, make it so smsc-ircc2 isn't loaded
> > automatically, and try this (along with my previous patch to swap
> > FIR and SIR):
> >
> > # dmesg -n 8
> > # echo 0x200 >
On Thursday 07 June 2007, Bjorn Helgaas wrote:
> On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> > I am beginning to doubt whether drier
> > works on my system at all (i.e. before PnP change); have to find time to
> > test.
>
> In 2.6.21, smsc-ircc2 at least found the device. So
On Friday 08 June 2007, Samuel Ortiz wrote:
> Hi Bjorn,
>
> On 6/7/2007, "Bjorn Helgaas" <[EMAIL PROTECTED]> wrote:
> >On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> >> On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> >> > On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov
On Friday 08 June 2007, Samuel Ortiz wrote:
Hi Bjorn,
On 6/7/2007, Bjorn Helgaas [EMAIL PROTECTED] wrote:
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
On
On Thursday 07 June 2007, Bjorn Helgaas wrote:
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
I am beginning to doubt whether drier
works on my system at all (i.e. before PnP change); have to find time to
test.
In 2.6.21, smsc-ircc2 at least found the device. So we
On Sunday 10 June 2007 02:03:03 am Andrey Borzenkov wrote:
Can you set CONFIG_ACPI_DEBUG=y, make it so smsc-ircc2 isn't loaded
automatically, and try this (along with my previous patch to swap
FIR and SIR):
# dmesg -n 8
# echo 0x200 /sys/module/acpi/parameters/debug_level
#
On Sunday 10 June 2007 12:47:07 am Andrey Borzenkov wrote:
Maybe we should also run the legacy probe when the PnP one fails. I
don't know how the preconfiguration stuff will behave with the device
being PnP enabled, but with your patch Andrey will still need to
modprobe smsc-ircc with
On Thursday 07 June 2007, Bjorn Helgaas wrote:
> In 2.6.21, smsc-ircc2 at least found the device. So we definitely have
> a problem because in 2.6.22-rc, we don't find the device.
>
> What laptop do you have? Maybe I can find one to play with.
>
This is Toshiba Portege 4000. The rest of your
Hi Bjorn,
On 6/7/2007, "Bjorn Helgaas" <[EMAIL PROTECTED]> wrote:
>On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
>> On Wednesday 06 June 2007, Bjorn Helgaas wrote:
>> > On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
>> > > On Wednesday 06 June 2007, Bjorn Helgaas
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> I am beginning to doubt whether drier
> works on my system at all (i.e. before PnP change); have to find time to
> test.
In 2.6.21, smsc-ircc2 at least found the device. So we definitely have
a problem because in 2.6.22-rc, we
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> > On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
> > > On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> > > > Something's wrong with this strategy. The BIOS is telling
On Thursday 07 June 2007 06:23:58 am Linus Walleij (LD/EAB) wrote:
> Björn wrote:
> > Something's wrong with this strategy. The BIOS is telling us
> > that an SMCf010 device is present, active, and responds at io
> > ports 0x100-0x107 and 0x2e8-0x2ef. The fact that it happens
> > to be on the
Björn wrote:
> Something's wrong with this strategy. The BIOS is telling us
> that an SMCf010 device is present, active, and responds at io
> ports 0x100-0x107 and 0x2e8-0x2ef. The fact that it happens
> to be on the other side of an ISA or LPC bridge should be
> immaterial to the OS
On Thursday 07 June 2007, Bjorn Helgaas wrote:
In 2.6.21, smsc-ircc2 at least found the device. So we definitely have
a problem because in 2.6.22-rc, we don't find the device.
What laptop do you have? Maybe I can find one to play with.
This is Toshiba Portege 4000. The rest of your
Björn wrote:
Something's wrong with this strategy. The BIOS is telling us
that an SMCf010 device is present, active, and responds at io
ports 0x100-0x107 and 0x2e8-0x2ef. The fact that it happens
to be on the other side of an ISA or LPC bridge should be
immaterial to the OS driver.
On Thursday 07 June 2007 06:23:58 am Linus Walleij (LD/EAB) wrote:
Björn wrote:
Something's wrong with this strategy. The BIOS is telling us
that an SMCf010 device is present, active, and responds at io
ports 0x100-0x107 and 0x2e8-0x2ef. The fact that it happens
to be on the other
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
Something's wrong with this strategy. The BIOS is telling us that an
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
I am beginning to doubt whether drier
works on my system at all (i.e. before PnP change); have to find time to
test.
In 2.6.21, smsc-ircc2 at least found the device. So we definitely have
a problem because in 2.6.22-rc, we don't
Hi Bjorn,
On 6/7/2007, Bjorn Helgaas [EMAIL PROTECTED] wrote:
On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
> > On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> > > Something's wrong with this strategy. The BIOS is telling us that an
> > > SMCf010 device is present, active, and responds at io
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
> On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> > Something's wrong with this strategy. The BIOS is telling us that an
> > SMCf010 device is present, active, and responds at io ports 0x100-0x107
> > and 0x2e8-0x2ef. The fact that it
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
Something's wrong with this strategy. The BIOS is telling us that an
SMCf010 device is present, active, and responds at io ports 0x100-0x107
and 0x2e8-0x2ef. The fact that it
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
Something's wrong with this strategy. The BIOS is telling us that an
SMCf010 device is present, active, and responds at io ports
On Tuesday 05 June 2007 05:57:30 am Linus Walleij (LD/EAB) wrote:
> You don't need to alter the defaults for the Toshiba ALi, the
> preconfigure will respect the settings from the commandline,
> e.g. modprobe smsc-ircc2 ircc_fir=0x100,ircc_sir=0x02e8.
>
> BUT this value just won't work: we don't
On 6/5/2007, "Linus Walleij (LD/EAB)" <[EMAIL PROTECTED]>
wrote:
>Sam wrote:
>
>> Andrey, in addition to Bjorn's patch, could you also apply
>> this one and try again:
>>
>> diff --git a/drivers/net/irda/smsc-ircc2.c
>> b/drivers/net/irda/smsc-ircc2.c index 31c6233..800562a 100644
>> ---
Andrey wrote:
> And here is what PnP tells us:
> {pts/1}% cat /sys/bus/pnp/devices/00:0a/options
> port 0x100-0x130, align 0xf, size 0x8, 16-bit address decoding irq
> 3,4,5,6,7,10,11 High-Edge dma 1,2,3 16-bit compatible
> Dependent: 01 - Priority acceptable
>port 0x3f8-0x3f8, align 0x0,
Sam wrote:
> Andrey, in addition to Bjorn's patch, could you also apply
> this one and try again:
>
> diff --git a/drivers/net/irda/smsc-ircc2.c
> b/drivers/net/irda/smsc-ircc2.c index 31c6233..800562a 100644
> --- a/drivers/net/irda/smsc-ircc2.c
> +++ b/drivers/net/irda/smsc-ircc2.c
> @@
Hi Linus,
On 6/5/2007, "Linus Walleij (LD/EAB)" <[EMAIL PROTECTED]>
wrote:
>> > Ok, FIR and SIR are definitey mixed up. So, now could you please
>try
>> > Bjorn's patch ?
>>
>> does not work.
>
>It looks like the purpose of the patch is to provide more printouts
>not to fix the problem,
> > Ok, FIR and SIR are definitey mixed up. So, now could you please
try
> > Bjorn's patch ?
>
> does not work.
It looks like the purpose of the patch is to provide more printouts
not to fix the problem, please mail your dmesg post-patch.
Linus
-
To unsubscribe from this list: send the line
Ok, FIR and SIR are definitey mixed up. So, now could you please
try
Bjorn's patch ?
does not work.
It looks like the purpose of the patch is to provide more printouts
not to fix the problem, please mail your dmesg post-patch.
Linus
-
To unsubscribe from this list: send the line
Hi Linus,
On 6/5/2007, Linus Walleij (LD/EAB) [EMAIL PROTECTED]
wrote:
Ok, FIR and SIR are definitey mixed up. So, now could you please
try
Bjorn's patch ?
does not work.
It looks like the purpose of the patch is to provide more printouts
not to fix the problem, please mail your dmesg
Sam wrote:
Andrey, in addition to Bjorn's patch, could you also apply
this one and try again:
diff --git a/drivers/net/irda/smsc-ircc2.c
b/drivers/net/irda/smsc-ircc2.c index 31c6233..800562a 100644
--- a/drivers/net/irda/smsc-ircc2.c
+++ b/drivers/net/irda/smsc-ircc2.c
@@ -2463,7
Andrey wrote:
And here is what PnP tells us:
{pts/1}% cat /sys/bus/pnp/devices/00:0a/options
port 0x100-0x130, align 0xf, size 0x8, 16-bit address decoding irq
3,4,5,6,7,10,11 High-Edge dma 1,2,3 16-bit compatible
Dependent: 01 - Priority acceptable
port 0x3f8-0x3f8, align 0x0, size
On 6/5/2007, Linus Walleij (LD/EAB) [EMAIL PROTECTED]
wrote:
Sam wrote:
Andrey, in addition to Bjorn's patch, could you also apply
this one and try again:
diff --git a/drivers/net/irda/smsc-ircc2.c
b/drivers/net/irda/smsc-ircc2.c index 31c6233..800562a 100644
---
On Tuesday 05 June 2007 05:57:30 am Linus Walleij (LD/EAB) wrote:
You don't need to alter the defaults for the Toshiba ALi, the
preconfigure will respect the settings from the commandline,
e.g. modprobe smsc-ircc2 ircc_fir=0x100,ircc_sir=0x02e8.
BUT this value just won't work: we don't know
On Tuesday 05 June 2007, Samuel Ortiz wrote:
> (Adding Linus Walleij, who wrote part of the smsc driver, to Cc:)
>
> On Mon, Jun 04, 2007 at 06:33:56AM +0400, Andrey Borzenkov wrote:
> > On Monday 04 June 2007, Samuel Ortiz wrote:
> > > It seems that PnP tells us that the FIR port is at 0x2e8
On Monday 04 June 2007, Bjorn Helgaas wrote:
> On Sunday 03 June 2007 02:16:05 am Andrey Borzenkov wrote:
> > On Sunday 03 June 2007, Andrey Borzenkov wrote:
> > > Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
> > > Nothing was changed in setup except kernel version.
> >
(Adding Linus Walleij, who wrote part of the smsc driver, to Cc:)
On Mon, Jun 04, 2007 at 06:33:56AM +0400, Andrey Borzenkov wrote:
> On Monday 04 June 2007, Samuel Ortiz wrote:
> > It seems that PnP tells us that the FIR port is at 0x2e8 while we're
> > expecting it at 0x2f8.
> > Could you apply
On Sunday 03 June 2007 02:16:05 am Andrey Borzenkov wrote:
> On Sunday 03 June 2007, Andrey Borzenkov wrote:
> > Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
> > Nothing was changed in setup except kernel version.
> >
> > 2.6.21:
> >
> > Detected unconfigured Toshiba
On Sunday 03 June 2007 02:16:05 am Andrey Borzenkov wrote:
On Sunday 03 June 2007, Andrey Borzenkov wrote:
Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
Nothing was changed in setup except kernel version.
2.6.21:
Detected unconfigured Toshiba laptop with ALi
(Adding Linus Walleij, who wrote part of the smsc driver, to Cc:)
On Mon, Jun 04, 2007 at 06:33:56AM +0400, Andrey Borzenkov wrote:
On Monday 04 June 2007, Samuel Ortiz wrote:
It seems that PnP tells us that the FIR port is at 0x2e8 while we're
expecting it at 0x2f8.
Could you apply this
On Monday 04 June 2007, Bjorn Helgaas wrote:
On Sunday 03 June 2007 02:16:05 am Andrey Borzenkov wrote:
On Sunday 03 June 2007, Andrey Borzenkov wrote:
Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
Nothing was changed in setup except kernel version.
2.6.21:
On Tuesday 05 June 2007, Samuel Ortiz wrote:
(Adding Linus Walleij, who wrote part of the smsc driver, to Cc:)
On Mon, Jun 04, 2007 at 06:33:56AM +0400, Andrey Borzenkov wrote:
On Monday 04 June 2007, Samuel Ortiz wrote:
It seems that PnP tells us that the FIR port is at 0x2e8 while we're
On Monday 04 June 2007, Samuel Ortiz wrote:
> Hi Andrey,
>
> On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote:
> > Adding "nopnp" parameters finds device just fine so it is apparently
> > result of this commit:
> >
> > commit d0d4f69bb65a8c1c1430c577a583632709b874c6
> > Author:
Hi Andrey,
On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote:
>
> Adding "nopnp" parameters finds device just fine so it is apparently result
> of
> this commit:
>
> commit d0d4f69bb65a8c1c1430c577a583632709b874c6
> Author: Bjorn Helgaas <[EMAIL PROTECTED]>
> Date: Tue May 8
On Sunday 03 June 2007, Andrey Borzenkov wrote:
> Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
> Nothing was changed in setup except kernel version.
>
> 2.6.21:
>
> Detected unconfigured Toshiba laptop with ALi ISA bridge SMSC IrDA chip,
> pre-configuring device.
>
Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
Nothing was changed in setup except kernel version.
2.6.21:
Detected unconfigured Toshiba laptop with ALi ISA bridge SMSC IrDA chip,
pre-configuring device.
Activated ALi 1533 ISA bridge port 0x02e8.
Activated ALi 1533 ISA
Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
Nothing was changed in setup except kernel version.
2.6.21:
Detected unconfigured Toshiba laptop with ALi ISA bridge SMSC IrDA chip,
pre-configuring device.
Activated ALi 1533 ISA bridge port 0x02e8.
Activated ALi 1533 ISA
On Sunday 03 June 2007, Andrey Borzenkov wrote:
Under 2.6.22-rc I lost irda0 interface - smsc claims no device present.
Nothing was changed in setup except kernel version.
2.6.21:
Detected unconfigured Toshiba laptop with ALi ISA bridge SMSC IrDA chip,
pre-configuring device.
Activated ALi
Hi Andrey,
On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote:
Adding nopnp parameters finds device just fine so it is apparently result
of
this commit:
commit d0d4f69bb65a8c1c1430c577a583632709b874c6
Author: Bjorn Helgaas [EMAIL PROTECTED]
Date: Tue May 8 00:36:05
On Monday 04 June 2007, Samuel Ortiz wrote:
Hi Andrey,
On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote:
Adding nopnp parameters finds device just fine so it is apparently
result of this commit:
commit d0d4f69bb65a8c1c1430c577a583632709b874c6
Author: Bjorn Helgaas
94 matches
Mail list logo
