On 3/5/15 19:40, Kalle Valo wrote:
> Rafał Miłecki writes:
>
>> Kalle, I guess the recent discussion and work on this problem could be
>> confusing, so let me try to sum it up it a bit.
>>
>> First of all, please note there are 3 awaiting bcma patches that
>> should be applied independently of
> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
> or will cause building break for allmodconfig under c6x:
>
> CC [M] drivers/bcma/driver_pcie2.o
> drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
> drivers/bcma/driver_pcie2.c:196:8: error:
Rafał Miłecki writes:
> Kalle, I guess the recent discussion and work on this problem could be
> confusing, so let me try to sum it up it a bit.
>
> First of all, please note there are 3 awaiting bcma patches that
> should be applied independently of what we decide to do with this
> patch. They
On 3/5/15 19:40, Kalle Valo wrote:
Rafał Miłecki zaj...@gmail.com writes:
Kalle, I guess the recent discussion and work on this problem could be
confusing, so let me try to sum it up it a bit.
First of all, please note there are 3 awaiting bcma patches that
should be applied independently
Rafał Miłecki zaj...@gmail.com writes:
Kalle, I guess the recent discussion and work on this problem could be
confusing, so let me try to sum it up it a bit.
First of all, please note there are 3 awaiting bcma patches that
should be applied independently of what we decide to do with this
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
drivers/bcma/driver_pcie2.c:196:8: error: implicit
On 3 March 2015 at 22:16, Chen Gang wrote:
> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
> or will cause building break for allmodconfig under c6x:
>
> CC [M] drivers/bcma/driver_pcie2.o
> drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
>
On Wed, 4 Mar 2015 14:36:10 +0100
Rafał Miłecki wrote:
> Any other opinions?
I think this is the only way to go.
In ssb we always had optional pcicore driver, as far as I remember,
so we should have the same in bcma, too.
The old WRT54G kernel used to compile just fine with SSB and without any
On 4 March 2015 at 17:38, Michael Büsch wrote:
> On Wed, 4 Mar 2015 14:36:10 +0100
> Rafał Miłecki wrote:
>
>> Any other opinions?
>
> I think this is the only way to go.
> In ssb we always had optional pcicore driver, as far as I remember,
> so we should have the same in bcma, too.
> The old
On 4 March 2015 at 13:08, Rafał Miłecki wrote:
> On 4 March 2015 at 07:19, Rafał Miłecki wrote:
>> On 3 March 2015 at 22:16, Chen Gang wrote:
>>> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
>>> or will cause building break for allmodconfig under c6x:
>>>
>>> CC
On 4 March 2015 at 07:19, Rafał Miłecki wrote:
> On 3 March 2015 at 22:16, Chen Gang wrote:
>> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
>> or will cause building break for allmodconfig under c6x:
>>
>> CC [M] drivers/bcma/driver_pcie2.o
>>
On Wed, 4 Mar 2015 14:36:10 +0100
Rafał Miłecki zaj...@gmail.com wrote:
Any other opinions?
I think this is the only way to go.
In ssb we always had optional pcicore driver, as far as I remember,
so we should have the same in bcma, too.
The old WRT54G kernel used to compile just fine with SSB
On 4 March 2015 at 17:38, Michael Büsch m...@bues.ch wrote:
On Wed, 4 Mar 2015 14:36:10 +0100
Rafał Miłecki zaj...@gmail.com wrote:
Any other opinions?
I think this is the only way to go.
In ssb we always had optional pcicore driver, as far as I remember,
so we should have the same in
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function
On 4 March 2015 at 07:19, Rafał Miłecki zaj...@gmail.com wrote:
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M]
On 4 March 2015 at 13:08, Rafał Miłecki zaj...@gmail.com wrote:
On 4 March 2015 at 07:19, Rafał Miłecki zaj...@gmail.com wrote:
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building
Sorry for my carelessness, I deleted the original reply mail to me (may
also deleted another mails to me, too).
The hotmail is not stable, I am just struggling with it (it can not work
well with linux-kernel@vger.kernel.org).
Could you forward your original reply to me again?
Thanks.
On
On 3 March 2015 at 22:16, Chen Gang wrote:
> bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
> or will cause building break for allmodconfig under c6x:
>
> CC [M] drivers/bcma/driver_pcie2.o
> drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
>
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
drivers/bcma/driver_pcie2.c:196:8: error: implicit declaration
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
drivers/bcma/driver_pcie2.c:196:8: error: implicit declaration
On 3 March 2015 at 22:16, Chen Gang xili_gchen_5...@hotmail.com wrote:
bcma also needs PCI, just like IOMEM and DMA, so let it depend on PCI,
or will cause building break for allmodconfig under c6x:
CC [M] drivers/bcma/driver_pcie2.o
drivers/bcma/driver_pcie2.c: In function
Sorry for my carelessness, I deleted the original reply mail to me (may
also deleted another mails to me, too).
The hotmail is not stable, I am just struggling with it (it can not work
well with linux-kernel@vger.kernel.org).
Could you forward your original reply to me again?
Thanks.
On
22 matches
Mail list logo