On 5/9/19 7:28 PM, Tomasz Maciej Nowak wrote:
Hi Jeff,
W dniu 09.05.2019 o 18:25, Jeff Kletsky pisze:
On 5/9/19 12:04 PM, Petr Štetiar wrote:
Jeff Kletsky [2019-05-09 11:23:18]:
I reconfirmed that
openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
openwrt$
Hi Jeff,
W dniu 09.05.2019 o 18:25, Jeff Kletsky pisze:
> On 5/9/19 12:04 PM, Petr Štetiar wrote:
>
>> Jeff Kletsky [2019-05-09 11:23:18]:
>>
>>> I reconfirmed that
>>>
>>> openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
>>> openwrt$ cat /dev/null > .config
>>>
On 5/9/19 12:04 PM, Petr Štetiar wrote:
Jeff Kletsky [2019-05-09 11:23:18]:
I reconfirmed that
openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
openwrt$ cat /dev/null > .config
openwrt$ make menuconfig
has the same behavior -- the nand target does not set
Jeff Kletsky [2019-05-09 11:23:18]:
> I reconfirmed that
>
> openwrt/target/linux/ath79$ cp generic/config-default nand/config-default
> openwrt$ cat /dev/null > .config
> openwrt$ make menuconfig
>
> has the same behavior -- the nand target does not set PCI_SUPPORT
it works here(tm):
On 5/9/19 10:49 AM, Robert Marko wrote:
I don't see any differences between the generic and nand subtargets'
`config-default`, `target.mk`, or `image/*.mk` that seem related to
PCI_SUPPORT.
Well, generic target has PCI symbols enabled in config-default
> I don't see any differences between the generic and nand subtargets'
> `config-default`, `target.mk`, or `image/*.mk` that seem related to
> PCI_SUPPORT.
Well, generic target has PCI symbols enabled in config-default
Jeff Kletsky [2019-05-09 10:29:31]:
Hi,
> I'm having some challenges understanding why PCI_SUPPORT is being set
> for the "generic" target, but not being set for the "nand" subtarget.
perhaps because nobody is using this nand subtarget, so nobody has noticed and
fixed it yet.
-- ynezz
I'm having some challenges understanding why PCI_SUPPORT is being set
for the "generic" target, but not being set for the "nand" subtarget.
This seems to be the cause for the ath10k drivers not being available
in menuconfig.
While this has become an issue with the first port of an ath79 device
