[OpenWrt-Devel] rc.local, inittab, rc.d not editable
Hi, Why all those files in /etc are not editable: rc.local, inittab, rc.d? How can I make them editable? Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
John, have you got time to look at it? Cheers, Le 9 mai 2016 18:58, "John Crispin" a écrit : > Hi Baptiste, > > on my list for this week > > John > > On 09/05/2016 18:56, Baptiste Clenet wrote: > > Lazar, > > Have you managed to make mt76 work on mt7688? > > > > Thanks > > > > 2016-05-03 1:52 GMT+02:00 Lazar Demin : > >> Marc, > >> Can you expand on what you did to get the AP to work? I'm completely > >> stumped... > >> > >> Any luck on the STA? > >> > >> > >> Thanks > >> > >> On Thu, Apr 21, 2016 at 3:00 PM, Marc Nicholas wrote: > >>> > >>> Is the firmware getting loaded (/lib/firmware/mt7628_e2.bin)? It looks > >>> like the fix in 48958 for this is in github.com/openwrt-mirror/ but > not > >>> in github.com/openwrt/. > >>> > >>> Yes, the firmware is getting loaded based on the boot logs. > >>> > >>> I’ve gotten a bit further and have AP mode running. But can’t for the > life > >>> of me get STA to work….can’t even scan for APs. :-/ > >>> > >>> Thanks! > >>> > >>> -m > >>> > >>> -- > >>> > >>> ___ > >>> openwrt-devel mailing list > >>> openwrt-devel@lists.openwrt.org > >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > >>> > >> > >> > >> ___ > >> openwrt-devel mailing list > >> openwrt-devel@lists.openwrt.org > >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > >> > > > > > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
2016-05-09 18:57 GMT+02:00 John Crispin : > Hi Baptiste, > > on my list for this week Ok John, let us know your set up to make mt76 as a wifi interface on mt7688, thanks. > > John > > On 09/05/2016 18:56, Baptiste Clenet wrote: >> Lazar, >> Have you managed to make mt76 work on mt7688? >> >> Thanks >> >> 2016-05-03 1:52 GMT+02:00 Lazar Demin : >>> Marc, >>> Can you expand on what you did to get the AP to work? I'm completely >>> stumped... >>> >>> Any luck on the STA? >>> >>> >>> Thanks >>> >>> On Thu, Apr 21, 2016 at 3:00 PM, Marc Nicholas wrote: >>>> >>>> Is the firmware getting loaded (/lib/firmware/mt7628_e2.bin)? It looks >>>> like the fix in 48958 for this is in github.com/openwrt-mirror/ but not >>>> in github.com/openwrt/. >>>> >>>> Yes, the firmware is getting loaded based on the boot logs. >>>> >>>> I’ve gotten a bit further and have AP mode running. But can’t for the life >>>> of me get STA to work….can’t even scan for APs. :-/ >>>> >>>> Thanks! >>>> >>>> -m >>>> >>>> -- >>>> >>>> ___ >>>> openwrt-devel mailing list >>>> openwrt-devel@lists.openwrt.org >>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>>> >>> >>> >>> ___ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> >> >> >> > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Lazar, Have you managed to make mt76 work on mt7688? Thanks 2016-05-03 1:52 GMT+02:00 Lazar Demin : > Marc, > Can you expand on what you did to get the AP to work? I'm completely > stumped... > > Any luck on the STA? > > > Thanks > > On Thu, Apr 21, 2016 at 3:00 PM, Marc Nicholas wrote: >> >> Is the firmware getting loaded (/lib/firmware/mt7628_e2.bin)? It looks >> like the fix in 48958 for this is in github.com/openwrt-mirror/ but not >> in github.com/openwrt/. >> >> Yes, the firmware is getting loaded based on the boot logs. >> >> I’ve gotten a bit further and have AP mode running. But can’t for the life >> of me get STA to work….can’t even scan for APs. :-/ >> >> Thanks! >> >> -m >> >> -- >> >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] UART1 mt7688
Found the solution ! Need to add uart1 in dts and set the clock Le 27 avr. 2016 09:24, "Baptiste Clenet" a écrit : > Hi, > > I want to run an UART communication between the mt7688 and another > board, console uses UART0 but I want to configure UART1 to be able to > send data on it. Currently, if I send something on /dev/ttyS1, I get: > write to fd 4 failed: I/O error > or > ash: write error: I/O error > > root@OpenWrt:/# stty -F /dev/ttyS1 > stty: /dev/ttyS1: I/O error > > Should I add something in the dts? > > Thanks > > -- > Baptiste > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] UART1 mt7688
Hi, I want to run an UART communication between the mt7688 and another board, console uses UART0 but I want to configure UART1 to be able to send data on it. Currently, if I send something on /dev/ttyS1, I get: write to fd 4 failed: I/O error or ash: write error: I/O error root@OpenWrt:/# stty -F /dev/ttyS1 stty: /dev/ttyS1: I/O error Should I add something in the dts? Thanks -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Will finish to try next week
Le 14 avr. 2016 20:20, "Baptiste Clenet" a écrit :
> 2016-04-14 16:58 GMT+02:00 John Crispin :
> >
> >
> > On 14/04/2016 16:38, Baptiste Clenet wrote:
> >> Marc, yes it has been added by John Crispins.
> >>
> >> I had nothing in etc/config/wireless, which is the right definition
> >> for this driver? (I don't find any documentation). Tom, Adam, yes it
> >> is defined.
> >>
> >> 2016-04-12 13:30 GMT+02:00 Adam Kent :
> >>> Hi Baptiste
> >>>
> >>> Which board exactly? You may need to add the "wmac" definition to the
> >>> relevant dts file. Have a look in
> >>> target/linux/ramips/dts/.dts and make sure there's
> >>> this:
> >>>
> >>> wmac@1030 {
> >>> status = "okay";
> >>> };
> >>>
> >>> - Adam
> >>>
> >>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
> wrote:
> >>>> Hi,
> >>>>
> >>>> I flashed the current tree on mt7688 board and no interface showed up
> >>>> for wifi. Should I do something? I would like to try the mt76 wifi
> >>>> driver on this board. (I added it with in menuconfig)
> >>>>
> >>>> Cheers,
> >>>>
> >>>> --
> >>>> Baptiste
> >>>> ___
> >>>> openwrt-devel mailing list
> >>>> openwrt-devel@lists.openwrt.org
> >>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
> >>
> >>
> >>
> >
> >
> > are you loading the mt76 driver ?
> modprobe mt76?
> It is already loaded:
> cfg80211 215619 3 mt7603e
> mac80211 389306 3 mt7603e
> mt76 15734 2 mt7603e
> mt7603e27964 0
> mt76x2e34300 0
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
> --
> Baptiste
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
2016-04-14 16:58 GMT+02:00 John Crispin :
>
>
> On 14/04/2016 16:38, Baptiste Clenet wrote:
>> Marc, yes it has been added by John Crispins.
>>
>> I had nothing in etc/config/wireless, which is the right definition
>> for this driver? (I don't find any documentation). Tom, Adam, yes it
>> is defined.
>>
>> 2016-04-12 13:30 GMT+02:00 Adam Kent :
>>> Hi Baptiste
>>>
>>> Which board exactly? You may need to add the "wmac" definition to the
>>> relevant dts file. Have a look in
>>> target/linux/ramips/dts/.dts and make sure there's
>>> this:
>>>
>>> wmac@1030 {
>>> status = "okay";
>>> };
>>>
>>> - Adam
>>>
>>> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet
>>> wrote:
>>>> Hi,
>>>>
>>>> I flashed the current tree on mt7688 board and no interface showed up
>>>> for wifi. Should I do something? I would like to try the mt76 wifi
>>>> driver on this board. (I added it with in menuconfig)
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Baptiste
>>>> ___
>>>> openwrt-devel mailing list
>>>> openwrt-devel@lists.openwrt.org
>>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>>
>>
>
>
> are you loading the mt76 driver ?
modprobe mt76?
It is already loaded:
cfg80211 215619 3 mt7603e
mac80211 389306 3 mt7603e
mt76 15734 2 mt7603e
mt7603e27964 0
mt76x2e34300 0
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Marc, yes it has been added by John Crispins.
I had nothing in etc/config/wireless, which is the right definition
for this driver? (I don't find any documentation). Tom, Adam, yes it
is defined.
2016-04-12 13:30 GMT+02:00 Adam Kent :
> Hi Baptiste
>
> Which board exactly? You may need to add the "wmac" definition to the
> relevant dts file. Have a look in
> target/linux/ramips/dts/.dts and make sure there's
> this:
>
> wmac@1030 {
> status = "okay";
> };
>
> - Adam
>
> On Tue, Apr 12, 2016 at 6:27 PM, Baptiste Clenet wrote:
>> Hi,
>>
>> I flashed the current tree on mt7688 board and no interface showed up
>> for wifi. Should I do something? I would like to try the mt76 wifi
>> driver on this board. (I added it with in menuconfig)
>>
>> Cheers,
>>
>> --
>> Baptiste
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] mt76 wifi module on mt7688 board, no interface
Hi, I flashed the current tree on mt7688 board and no interface showed up for wifi. Should I do something? I would like to try the mt76 wifi driver on this board. (I added it with in menuconfig) Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB Hotplug
2016-03-16 14:46 GMT+01:00 John Crispin : > > > On 16/03/2016 14:25, Baptiste Clenet wrote: >> 2016-03-07 15:19 GMT+01:00 John Crispin : >>> >>> >>> On 07/03/2016 15:00, Baptiste Clenet wrote: >>>> 2016-03-07 9:51 GMT+01:00 John Crispin : >>>>> >>>>> >>>>> On 07/03/2016 09:47, Baptiste Clenet wrote: >>>>>> 2016-03-04 18:24 GMT+01:00 John Crispin : >>>>>>> >>>>>>> >>>>>>> On 04/03/2016 17:50, Baptiste Clenet wrote: >>>>>>>> We don't use the current tree but a version from November. >>>>>>>> You're talking about this changeset: >>>>>>>> https://dev.openwrt.org/changeset/48749 >>>>>>>> >>>>>>>> I will apply it and let you know if it is better. >>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>>> >>>>>>> yep, try adding that one please and see if that fixes the issue >>>>>>> ___ >>>>>>> openwrt-devel mailing list >>>>>>> openwrt-devel@lists.openwrt.org >>>>>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>>>>> >>>>>> John, I chose Default profile for mt7688 board and it has built an >>>>>> image named "openwrt-ramips-mt7688-LinkIt7688-squashfs-sysupgrade.bin", >>>>>> so it used the LINKIT7688 dts instead of MT7628 dts. >>>>>> >>>>>> Concerning USB, I see the same behaviour, if the pendrive is plugged >>>>>> between the boot, it works and I can plug it in and out as much as I >>>>>> can, however, it the board boots and then I insert the pendrive, it is >>>>>> not detected (the pendrive's led switches on for 1/2sec and then >>>>>> switches off. >>>>> >>>>> seen this before while building pcbs .. so my money is on the following >>>>> theory: your power supply is failing to provide enough current quickly >>>>> enough for the USB to come up causing OC protection or similar to shut >>>>> it down. check your supply voltage of the usb port with a scope and you >>>>> will probably see it breakdown after that 1/2 s >>>> >>>> Yes it was a hardware problem effectively, I added a protection chip >>>> which did not work properly and caused the pendrive not to be >>>> detected. I removed it and it works, so I will dig into the hardware >>>> problem. >>>> Thanks >>> >>> we are a software project so awesome we can even remote debug hardware >>> problems :-) >>> >>> >>>>> >>>>> >>>>> >>>>> >>>>>> Second question; I see you added the mt76 wifi driver which is great! >>>>>> Thank you for your work. I see the module added on the board, how may >>>>>> I up the wifi? (I didn't find any readme on github [1]) >>>>> >>>>> its a normal mac80211 based wifi so use the normal method. you will need >>>>> to add a eeprom offset to the dts file. either figure it out yourself >>>>> (look at how mt7620 based boards do it) or wait a few days till i had >>>>> time to update the lks7688 profile. >> >> John, have you had time to update mt7688 board for wifi setup? >> > > let me check the commit log for you ... > > ... nope i cant find a commit that adds the support ;) i hope to have > time start of next week. > Ok, could you let me know when you're done with that please? Thanks >>>>> >>>> I let you do the edits and I will try as soon as you've done it. >>>> Thanks for your help >>> >>> ok >> >> >> -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB Hotplug
2016-03-07 15:19 GMT+01:00 John Crispin : > > > On 07/03/2016 15:00, Baptiste Clenet wrote: >> 2016-03-07 9:51 GMT+01:00 John Crispin : >>> >>> >>> On 07/03/2016 09:47, Baptiste Clenet wrote: >>>> 2016-03-04 18:24 GMT+01:00 John Crispin : >>>>> >>>>> >>>>> On 04/03/2016 17:50, Baptiste Clenet wrote: >>>>>> We don't use the current tree but a version from November. >>>>>> You're talking about this changeset: >>>>>> https://dev.openwrt.org/changeset/48749 >>>>>> >>>>>> I will apply it and let you know if it is better. >>>>>> >>>>>>>>>> >>>>> >>>>> >>>>> yep, try adding that one please and see if that fixes the issue >>>>> ___ >>>>> openwrt-devel mailing list >>>>> openwrt-devel@lists.openwrt.org >>>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>>> >>>> John, I chose Default profile for mt7688 board and it has built an >>>> image named "openwrt-ramips-mt7688-LinkIt7688-squashfs-sysupgrade.bin", >>>> so it used the LINKIT7688 dts instead of MT7628 dts. >>>> >>>> Concerning USB, I see the same behaviour, if the pendrive is plugged >>>> between the boot, it works and I can plug it in and out as much as I >>>> can, however, it the board boots and then I insert the pendrive, it is >>>> not detected (the pendrive's led switches on for 1/2sec and then >>>> switches off. >>> >>> seen this before while building pcbs .. so my money is on the following >>> theory: your power supply is failing to provide enough current quickly >>> enough for the USB to come up causing OC protection or similar to shut >>> it down. check your supply voltage of the usb port with a scope and you >>> will probably see it breakdown after that 1/2 s >> >> Yes it was a hardware problem effectively, I added a protection chip >> which did not work properly and caused the pendrive not to be >> detected. I removed it and it works, so I will dig into the hardware >> problem. >> Thanks > > we are a software project so awesome we can even remote debug hardware > problems :-) > > >>> >>> >>> >>> >>>> Second question; I see you added the mt76 wifi driver which is great! >>>> Thank you for your work. I see the module added on the board, how may >>>> I up the wifi? (I didn't find any readme on github [1]) >>> >>> its a normal mac80211 based wifi so use the normal method. you will need >>> to add a eeprom offset to the dts file. either figure it out yourself >>> (look at how mt7620 based boards do it) or wait a few days till i had >>> time to update the lks7688 profile. John, have you had time to update mt7688 board for wifi setup? >>> >> I let you do the edits and I will try as soon as you've done it. >> Thanks for your help > > ok -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB Hotplug
2016-03-07 9:51 GMT+01:00 John Crispin : > > > On 07/03/2016 09:47, Baptiste Clenet wrote: >> 2016-03-04 18:24 GMT+01:00 John Crispin : >>> >>> >>> On 04/03/2016 17:50, Baptiste Clenet wrote: >>>> We don't use the current tree but a version from November. >>>> You're talking about this changeset: >>>> https://dev.openwrt.org/changeset/48749 >>>> >>>> I will apply it and let you know if it is better. >>>> >>>>>>>> >>> >>> >>> yep, try adding that one please and see if that fixes the issue >>> ___ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> >> John, I chose Default profile for mt7688 board and it has built an >> image named "openwrt-ramips-mt7688-LinkIt7688-squashfs-sysupgrade.bin", >> so it used the LINKIT7688 dts instead of MT7628 dts. >> >> Concerning USB, I see the same behaviour, if the pendrive is plugged >> between the boot, it works and I can plug it in and out as much as I >> can, however, it the board boots and then I insert the pendrive, it is >> not detected (the pendrive's led switches on for 1/2sec and then >> switches off. > > seen this before while building pcbs .. so my money is on the following > theory: your power supply is failing to provide enough current quickly > enough for the USB to come up causing OC protection or similar to shut > it down. check your supply voltage of the usb port with a scope and you > will probably see it breakdown after that 1/2 s Yes it was a hardware problem effectively, I added a protection chip which did not work properly and caused the pendrive not to be detected. I removed it and it works, so I will dig into the hardware problem. Thanks > > > > >> Second question; I see you added the mt76 wifi driver which is great! >> Thank you for your work. I see the module added on the board, how may >> I up the wifi? (I didn't find any readme on github [1]) > > its a normal mac80211 based wifi so use the normal method. you will need > to add a eeprom offset to the dts file. either figure it out yourself > (look at how mt7620 based boards do it) or wait a few days till i had > time to update the lks7688 profile. > I let you do the edits and I will try as soon as you've done it. Thanks for your help > > >> Cheers, >> >> [1] https://github.com/openwrt/mt76 >> >> -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB Hotplug
2016-03-04 18:24 GMT+01:00 John Crispin : > > > On 04/03/2016 17:50, Baptiste Clenet wrote: >> We don't use the current tree but a version from November. >> You're talking about this changeset: >> https://dev.openwrt.org/changeset/48749 >> >> I will apply it and let you know if it is better. >> >>>> >> > > > yep, try adding that one please and see if that fixes the issue > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel John, I chose Default profile for mt7688 board and it has built an image named "openwrt-ramips-mt7688-LinkIt7688-squashfs-sysupgrade.bin", so it used the LINKIT7688 dts instead of MT7628 dts. Concerning USB, I see the same behaviour, if the pendrive is plugged between the boot, it works and I can plug it in and out as much as I can, however, it the board boots and then I insert the pendrive, it is not detected (the pendrive's led switches on for 1/2sec and then switches off. Second question; I see you added the mt76 wifi driver which is great! Thank you for your work. I see the module added on the board, how may I up the wifi? (I didn't find any readme on github [1]) Cheers, [1] https://github.com/openwrt/mt76 -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] USB Hotplug
2016-03-04 16:57 GMT+01:00 John Crispin : > > > On 04/03/2016 16:43, John Crispin wrote: >> >> >> On 04/03/2016 16:42, alzhao wrote: >>> Hi john, >>> can you specify which patch? I want to check. >>> On Fri, 4 Mar 2016 at 23:34, John Crispin >> <mailto:blo...@openwrt.org>> wrote: >>> >>> >>> >>> On 04/03/2016 15:07, alzhao wrote: >>> > Did you develop the board by yourself? Generally this is a hardware >>> > problem, like wrong resistors. After the system boot the USB cannot >>> > supply enough power to the drive. Yes we did. Which size should we use? >>> > >>> > >>> > On Fri, 4 Mar 2016 at 21:57, Baptiste Clenet >> <mailto:bapcle...@gmail.com> >>> > <mailto:bapcle...@gmail.com <mailto:bapcle...@gmail.com>>> wrote: >>> > >>> > Hi, >>> > >>> > I run OpenWRT on a mt7688 board, if I plug a pendrive before >>> the boot, >>> > it is detected and I can store data on it. However, after the >>> board >>> > has finished booting, if I plug the pendrive, I can't detect >>> it, the >>> > LED on the pendrive switch on and off after a 1/2 sec. >>> > Should I include something else to make hotplug work? >>> > root@OpenWrt:/# lsmod | grep usb >>> > btintel 1209 1 btusb >>> > btusb 26816 0 >>> > ledtrig_usbdev 1936 0 >>> > nls_base5008 1 usbcore >>> > scsi_mod 90601 2 usb_storage >>> > usb_common 1740 1 usbcore >>> > usb_storage37407 0 >>> > usbcore 117268 7 btusb >>> > >>> > >>> > -- >>> > Baptiste >>> > ___ >>> > openwrt-devel mailing list >>> > openwrt-devel@lists.openwrt.org >>> <mailto:openwrt-devel@lists.openwrt.org> >>> <mailto:openwrt-devel@lists.openwrt.org >>> <mailto:openwrt-devel@lists.openwrt.org>> >>> > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> > >>> >>> what revision of openwrt do you use ? i recently pushed a patch that >>> fixes a phy reset problem causing usb2.0 devices to not work properly >>> We don't use the current tree but a version from November. You're talking about this changeset: https://dev.openwrt.org/changeset/48749 I will apply it and let you know if it is better. >> >> please don't top post and use HEAD revision or check the git log please >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > > in the case where it does not work, do you get IRQs from the USB ? > check /proc/interrupts to see if they increase please Nope, when I plug the pendrive, no more IRQ it stays at 47 root@OpenWrt:~# cat /proc/interrupts CPU0 5: 8954 MIPS 5 1010.ethernet 6: 73558 MIPS 6 ra0 7:1165498 MIPS 7 timer 22: 3429 INTC 14 1013.sdhci 25: 6 INTC 17 esw 26: 47 INTC 18 ehci_hcd:usb1, ohci_hcd:usb2 28:778 INTC 20 serial > > John > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] USB Hotplug
Hi, I run OpenWRT on a mt7688 board, if I plug a pendrive before the boot, it is detected and I can store data on it. However, after the board has finished booting, if I plug the pendrive, I can't detect it, the LED on the pendrive switch on and off after a 1/2 sec. Should I include something else to make hotplug work? root@OpenWrt:/# lsmod | grep usb btintel 1209 1 btusb btusb 26816 0 ledtrig_usbdev 1936 0 nls_base5008 1 usbcore scsi_mod 90601 2 usb_storage usb_common 1740 1 usbcore usb_storage37407 0 usbcore 117268 7 btusb -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Soletta Project on Openwrt
Hi, I don't know if you know the project Soletta: https://solettaproject.org/ I didn't see it as a package for OpenWRT, I wonder if anybody is working on it? They port it to Yocto project so it seems reasonable to create a package for openwrt, don't you think? Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Intel Edison port
Hi, Is anyone working on the port of Intel Edison on OpenWRT? And what is the status? Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Kernel 4.3, MT7688 does not boot
John, have you add time to try v4.3 kernel? 2015-12-30 19:13 GMT+01:00 John Crispin : > > On 30/12/2015 17:37, Baptiste Clenet wrote: >> Hi, >> >> I'm using a custom board including a MT7688 chip, I made the image >> with the latest openwrt build (I've just downloaded it), I got an >> image of 2,9Mo. >> >> I flashed it and here is the debug: >> >> ## Booting image at bc05 ... >>Image Name: MIPS OpenWrt Linux-4.3 >>Image Type: MIPS Linux Kernel Image (lzma compressed) >>Data Size:1294087 Bytes = 1.2 MB >>Load Address: 8000 >>Entry Point: 8000 >>Verifying Checksum ... OK >>Uncompressing Kernel Image ... OK >> No initrd >> ## Transferring control to Linux (at address 8000) ... >> ## Giving linux memsize in MB, 128 >> > > Hi, > > have not tried the lks since the v4.3 bump. will do so in new year. if > you cant wait, use CC, i tested the support only a few days ago. > > John -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Kernel 4.3, MT7688 does not boot
Hi, I'm using a custom board including a MT7688 chip, I made the image with the latest openwrt build (I've just downloaded it), I got an image of 2,9Mo. I flashed it and here is the debug: ## Booting image at bc05 ... Image Name: MIPS OpenWrt Linux-4.3 Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size:1294087 Bytes = 1.2 MB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK No initrd ## Transferring control to Linux (at address 8000) ... ## Giving linux memsize in MB, 128 Starting kernel ... [0.00] Linux version 4.3.0 (root@ubuntu) (gcc version 5.2.0 (OpenWrt GCC 5.2.0 r48016) ) #1 Wed Dec 30 17:23:51 CET 2015 [0.00] Board has SDRAM [0.00] Analog PMU set to hw control [0.00] Digital PMU set to hw control [0.00] SoC Type: MediaTek MT7688 ver:1 eco:2 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 00019655 (MIPS 24KEc) [0.00] MIPS: machine is MediaTek LinkIt Smart 7688 [0.00] Determined physical RAM map: [0.00] memory: 0800 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x07ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x07ff] [0.00] Initmem setup node 0 [mem 0x-0x07ff] [0.00] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: console=ttyS2,57600 rootfstype=squashfs,jffs2 [0.00] PID hash table entries: 512 (order: -1, 2048 bytes) [0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Writing ErrCtl register=00069e8c [0.00] Readback ErrCtl register=00069e8c [0.00] Memory: 125876K/131072K available (2911K kernel code, 123K rwdata, 584K rodata, 148K init, 196K bss, 5196K reserved, 0K cma-reserved) [0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] NR_IRQS:256 [0.00] intc: using register map from devicetree [0.00] CPU Clock: 580MHz [0.00] clocksource_of_init: no matching clocksources found [0.00] clocksource: MIPS: mask: 0x max_cycles: 0x, max_idle_ns: 6590553264 ns [0.12] sched_clock: 32 bits at 290MHz, resolution 3ns, wraps every 7405115902ns [0.015352] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216) [0.080523] pid_max: default: 32768 minimum: 301 [0.089784] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.102733] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.122840] clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1911260446275 ns [0.142376] pinctrl core: initialized pinctrl subsystem [0.153331] NET: Registered protocol family 16 [0.183464] mt7621_gpio 1600.gpio: registering 32 gpios [0.194573] mt7621_gpio 1600.gpio: registering 32 gpios [0.205588] mt7621_gpio 1600.gpio: registering 32 gpios [0.218222] clocksource: Switched to clocksource MIPS [0.229708] NET: Registered protocol family 2 [0.239172] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.252872] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.265393] TCP: Hash tables configured (established 1024 bind 1024) [0.278040] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.289496] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.302142] NET: Registered protocol family 1 [0.312126] futex hash table entries: 256 (order: -1, 3072 bytes) [0.344807] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.356277] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.378614] io scheduler noop registered [0.386235] io scheduler deadline registered (default) [0.397333] rt2880-pinmux pinctrl: invalid group "pwm0" for function "pwm0" [0.411019] rt2880-pinmux pinctrl: invalid group "pwm1" for function "pwm1" [0.425214] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.439137] rt2880-pinmux pinctrl: function 'uart0' not supported [0.451093] rt2880-pinmux pinctrl: invalid function uart0 in map table [0.464224] 1c00.uartlite: ttyS0 at MMIO 0x1c00 (irq = 28, base_baud = 250) is a 16550A [0.482375] rt2880-pinmux pinctrl: function 'uart1' not supported [0.494318] rt2880-pinmux pinctrl: invalid function uart1 in map table [0.507246] of_s
Re: [OpenWrt-Devel] MT7628, IRQ GPIO
2015-12-30 11:52 GMT+01:00 Baptiste Clenet : > Hi, > > I'm working on the MT7628 board and I try to register GPIO's irq. (I > haven't updated to kernel 4.3, I'm still on the previous version 3.18) > I've got two interrupts on GPIO 15 and GPIO 46. I see that to register > the interrupts it uses the internal GPIO interrupts (number 6). The > fact is, it register one handler for internal GPIO so whenever any of > the GPIO's irq (GPIO 15 or 46) are triggered, it always calls the same > handler. > Does it make sense? I may explain differently if it's not clear. > > How could I register both handlers? Is there a GPIO-IRQ driver which > handle IRQ from GPIO? > > By the way, thank you for your work on porting mt7628 to kernel 4.3, > I'm excited to try! > > Cheers, > > -- > Baptiste As far as I can see in [1], it seems that it has been implemented with the new patches. Is that right? [1] https://dev.openwrt.org/browser/trunk/target/linux/ramips/patches-4.3/0028-GPIO-ralink-add-mt7621-gpio-controller.patch -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] MT7628, IRQ GPIO
Hi, I'm working on the MT7628 board and I try to register GPIO's irq. (I haven't updated to kernel 4.3, I'm still on the previous version 3.18) I've got two interrupts on GPIO 15 and GPIO 46. I see that to register the interrupts it uses the internal GPIO interrupts (number 6). The fact is, it register one handler for internal GPIO so whenever any of the GPIO's irq (GPIO 15 or 46) are triggered, it always calls the same handler. Does it make sense? I may explain differently if it's not clear. How could I register both handlers? Is there a GPIO-IRQ driver which handle IRQ from GPIO? By the way, thank you for your work on porting mt7628 to kernel 4.3, I'm excited to try! Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firmaware size MT7628
2015-10-20 21:03 GMT+02:00 Baptiste Clenet : > 2015-10-20 20:28 GMT+02:00 Baptiste Clenet : >> Hi, >> >> I edited the firmware size of the MT7628 board from 4 to 16Mo because >> I've got 16Mo flash. I began with 8Mo ant it worked well but 16Mo >> seems to make the board crash at boot with error messages: >> >> [0.859932] jffs2: Flash size not aligned to erasesize, reducing to >> 6720KiB >> [0.874195] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x: 0x7368 instead >> [0.892987] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x0004: 0x0551 instead >> ... >> [1.043215] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x0030: 0xfb3a instead >> [1.061987] jffs2: Further such events for this erase block will >> not be printed >> [1.080861] jffs2: Empty flash at 0x0038 ends at 0x0040 >> [1.164315] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x0001: 0xadd7 instead >> [1.183110] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x00010004: 0x7f0d instead >> ... >> [1.611456] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 >> not found at 0x00020024: 0xeae7 instead >> [1.630228] jffs2: Further such events for this erase block will >> not be printed >> [1.691809] jffs2: Old JFFS2 bitmask found at 0x000295cc >> [1.702326] jffs2: You cannot use older JFFS2 filesystems with newer >> kernels >> >> I don't know if the problem comes from the flash driver or something >> else. Any input would be great if you have already encountered this >> problem? > > I edited the Makefile in target/linux/ramips/image: > Image/Build/Profile/MT7628=$(call > BuildFirmware/Default4M/$(1),$(1),mt7628,MT7628) > To > Image/Build/Profile/MT7628=$(call > BuildFirmware/Default16M/$(1),$(1),mt7628,MT7628) >> >> Regards, >> >> -- >> Baptiste > > > > -- > Baptiste Found out my problem by editing the .dts file -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Firmaware size MT7628
2015-10-20 20:28 GMT+02:00 Baptiste Clenet : > Hi, > > I edited the firmware size of the MT7628 board from 4 to 16Mo because > I've got 16Mo flash. I began with 8Mo ant it worked well but 16Mo > seems to make the board crash at boot with error messages: > > [0.859932] jffs2: Flash size not aligned to erasesize, reducing to 6720KiB > [0.874195] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x: 0x7368 instead > [0.892987] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x0004: 0x0551 instead > ... > [1.043215] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x0030: 0xfb3a instead > [1.061987] jffs2: Further such events for this erase block will > not be printed > [1.080861] jffs2: Empty flash at 0x0038 ends at 0x0040 > [1.164315] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x0001: 0xadd7 instead > [1.183110] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x00010004: 0x7f0d instead > ... > [1.611456] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 > not found at 0x00020024: 0xeae7 instead > [1.630228] jffs2: Further such events for this erase block will > not be printed > [1.691809] jffs2: Old JFFS2 bitmask found at 0x000295cc > [1.702326] jffs2: You cannot use older JFFS2 filesystems with newer > kernels > > I don't know if the problem comes from the flash driver or something > else. Any input would be great if you have already encountered this > problem? I edited the Makefile in target/linux/ramips/image: Image/Build/Profile/MT7628=$(call BuildFirmware/Default4M/$(1),$(1),mt7628,MT7628) To Image/Build/Profile/MT7628=$(call BuildFirmware/Default16M/$(1),$(1),mt7628,MT7628) > > Regards, > > -- > Baptiste -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Firmaware size MT7628
Hi, I edited the firmware size of the MT7628 board from 4 to 16Mo because I've got 16Mo flash. I began with 8Mo ant it worked well but 16Mo seems to make the board crash at boot with error messages: [0.859932] jffs2: Flash size not aligned to erasesize, reducing to 6720KiB [0.874195] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x: 0x7368 instead [0.892987] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0004: 0x0551 instead ... [1.043215] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0030: 0xfb3a instead [1.061987] jffs2: Further such events for this erase block will not be printed [1.080861] jffs2: Empty flash at 0x0038 ends at 0x0040 [1.164315] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001: 0xadd7 instead [1.183110] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010004: 0x7f0d instead ... [1.611456] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020024: 0xeae7 instead [1.630228] jffs2: Further such events for this erase block will not be printed [1.691809] jffs2: Old JFFS2 bitmask found at 0x000295cc [1.702326] jffs2: You cannot use older JFFS2 filesystems with newer kernels I don't know if the problem comes from the flash driver or something else. Any input would be great if you have already encountered this problem? Regards, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] i2c device not in /dev
Works now! Think the .dts wasn't taken into account correctly. 2015-09-15 17:32 GMT+02:00 Baptiste Clenet : > 2015-09-15 13:57 GMT+02:00 Baptiste Clenet : >> 2015-09-14 20:17 GMT+02:00 John Crispin : >>> >>> >>> On 14/09/2015 20:09, Daniel Golle wrote: >>>> On Mon, Sep 14, 2015 at 07:47:08PM +0200, John Crispin wrote: >>>>> On 14/09/2015 19:28, Baptiste Clenet wrote: >>>>>> Hi, >>>>>> >>>>>> I'm using a MT7628 chip and I try to implement an I2C device which >>>>>> will use i2c-ralink adapter. I registered my i2c device with >>>>>> module_i2c_driver(i2c_device_driver); >>>>>> >>>>>> I can see it on my bus: >>>>>> ./sys/bus/i2c/drivers/i2c_device_driver >>>>>> But it doesn't appear in /dev. >>>>>> >>>>>> What am I doing wrong? >>>>>> >>>>>> Regards, >>>>>> >>>>> >>>>> you are missing CONFIG_I2C_CHARDEV in the kernel config >>>> >>>> or maybe i2c-dev isn't loaded? try >>>> modprobe i2c-dev >>>> >>> >>> i2c-dev is part of i2c-core if that symbol is selected. i2c-core uses >>> AutoLoad and not AutoProbe so it should always load. >> >> Thnaks for the answer. >> >> i2c-dev and i2c-core are loaded as well as i2c-ralink and my i2c >> driver. How to add CONFIG_I2C_CHARDEV? I added it in >> /target/linux/ramips config file of my board but it hasn't changed >> anything. How may I check that the config has really been added? >> >> By the way, is there a similar CONFIG for SPI, like CONFIG_SPI_CHARDEV ? >> >>> >>> John >>> ___ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> >> >> >> -- >> Baptiste > > > Actually, here is my configuration: > I've got my driver in /sys/bus/i2c/drivers > Nothing in /sys/bus/i2c/devices > Nothing in /sys/class/i2c-dev as well. > > Concerning CONFIG_I2C_CHARDEV, it seems that it is automatically added > with i2c-core so it should be compiled in my distrib. (Do you know how > I can check?) > > Cheers, > > > -- > Baptiste The probleme was not in my driver file but in the adapter file, i2c-dev.h was not included. -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] i2c device not in /dev
2015-09-15 13:57 GMT+02:00 Baptiste Clenet : > 2015-09-14 20:17 GMT+02:00 John Crispin : >> >> >> On 14/09/2015 20:09, Daniel Golle wrote: >>> On Mon, Sep 14, 2015 at 07:47:08PM +0200, John Crispin wrote: >>>> On 14/09/2015 19:28, Baptiste Clenet wrote: >>>>> Hi, >>>>> >>>>> I'm using a MT7628 chip and I try to implement an I2C device which >>>>> will use i2c-ralink adapter. I registered my i2c device with >>>>> module_i2c_driver(i2c_device_driver); >>>>> >>>>> I can see it on my bus: >>>>> ./sys/bus/i2c/drivers/i2c_device_driver >>>>> But it doesn't appear in /dev. >>>>> >>>>> What am I doing wrong? >>>>> >>>>> Regards, >>>>> >>>> >>>> you are missing CONFIG_I2C_CHARDEV in the kernel config >>> >>> or maybe i2c-dev isn't loaded? try >>> modprobe i2c-dev >>> >> >> i2c-dev is part of i2c-core if that symbol is selected. i2c-core uses >> AutoLoad and not AutoProbe so it should always load. > > Thnaks for the answer. > > i2c-dev and i2c-core are loaded as well as i2c-ralink and my i2c > driver. How to add CONFIG_I2C_CHARDEV? I added it in > /target/linux/ramips config file of my board but it hasn't changed > anything. How may I check that the config has really been added? > > By the way, is there a similar CONFIG for SPI, like CONFIG_SPI_CHARDEV ? > >> >> John >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > -- > Baptiste Actually, here is my configuration: I've got my driver in /sys/bus/i2c/drivers Nothing in /sys/bus/i2c/devices Nothing in /sys/class/i2c-dev as well. Concerning CONFIG_I2C_CHARDEV, it seems that it is automatically added with i2c-core so it should be compiled in my distrib. (Do you know how I can check?) Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] i2c device not in /dev
2015-09-14 20:17 GMT+02:00 John Crispin : > > > On 14/09/2015 20:09, Daniel Golle wrote: >> On Mon, Sep 14, 2015 at 07:47:08PM +0200, John Crispin wrote: >>> On 14/09/2015 19:28, Baptiste Clenet wrote: >>>> Hi, >>>> >>>> I'm using a MT7628 chip and I try to implement an I2C device which >>>> will use i2c-ralink adapter. I registered my i2c device with >>>> module_i2c_driver(i2c_device_driver); >>>> >>>> I can see it on my bus: >>>> ./sys/bus/i2c/drivers/i2c_device_driver >>>> But it doesn't appear in /dev. >>>> >>>> What am I doing wrong? >>>> >>>> Regards, >>>> >>> >>> you are missing CONFIG_I2C_CHARDEV in the kernel config >> >> or maybe i2c-dev isn't loaded? try >> modprobe i2c-dev >> > > i2c-dev is part of i2c-core if that symbol is selected. i2c-core uses > AutoLoad and not AutoProbe so it should always load. Thnaks for the answer. i2c-dev and i2c-core are loaded as well as i2c-ralink and my i2c driver. How to add CONFIG_I2C_CHARDEV? I added it in /target/linux/ramips config file of my board but it hasn't changed anything. How may I check that the config has really been added? By the way, is there a similar CONFIG for SPI, like CONFIG_SPI_CHARDEV ? > > John > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] i2c device not in /dev
Hi, I'm using a MT7628 chip and I try to implement an I2C device which will use i2c-ralink adapter. I registered my i2c device with module_i2c_driver(i2c_device_driver); I can see it on my bus: ./sys/bus/i2c/drivers/i2c_device_driver But it doesn't appear in /dev. What am I doing wrong? Regards, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] wpan-tools: bump to wpan-tools-0.5
2015-08-24 5:30 GMT+02:00 Varka Bhadram : > Signed-off-by: Varka Bhadram > --- > package/network/utils/wpan-tools/Makefile |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/package/network/utils/wpan-tools/Makefile > b/package/network/utils/wpan-tools/Makefile > index 87a5fb1..6c2559d 100644 > --- a/package/network/utils/wpan-tools/Makefile > +++ b/package/network/utils/wpan-tools/Makefile > @@ -8,11 +8,11 @@ > include $(TOPDIR)/rules.mk > > PKG_NAME:=wpan-tools > -PKG_VERSION:=0.4 > +PKG_VERSION:=0.5 > > PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 > PKG_SOURCE_URL:=http://wpan.cakelab.org/releases/ > -PKG_MD5SUM:=37575523d1543e06b11295f03a891fa7 > +PKG_MD5SUM:=6226df405a98c13ec41bf4d1f0777d6b > > include $(INCLUDE_DIR)/package.mk > > -- > 1.7.9.5 > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Which version of the kernel is required to use wpan tools 0.5 at least? -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Mount mmc block
2015-08-18 20:39 GMT+02:00 : > On Tue, 18 Aug 2015 11:59:11 +0200 > Baptiste Clenet wrote: > >> mount -t -ext3 /dev/mmcblk0p1 /mnt/mmc/ I tried with FAT16 as well > > is ist better so? > > mount -t ext3 /dev/mmcblk0p1 /mnt/mmc/ > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > The solution was to format the emmc and create an ext4 file system. Thanks. -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Mount mmc block
2015-08-18 11:59 GMT+02:00 Baptiste Clenet : > Hi, > > I'm trying to mount a emmc block on /mnt/mmc on a Ralink MT7628 board: > > root@OpenWrt:/# ls /dev/mmcblk0p1 > /dev/mmcblk0p1 > root@OpenWrt:/# ls /mnt/mmc/ > root@OpenWrt:/# mount -t -ext3 /dev/mmcblk0p1 /mnt/mmc/ > mount: mounting /dev/mmcblk0p1 on /mnt/mmc/ failed: No such device > > Am I missing something here? /mnt/mmc and /dev/mmcblk0p1 both exist. > > Regards, > > -- > Baptiste I'm using Kernel 4.1.0 btw. I tried to find the filesystem of /dev/mmcblk0p1 with root@OpenWrt:/# tune2fs -l /dev/mmcblk0p1 tune2fs 1.42.12 (29-Aug-2014) tune2fs: Bad magic number in super-block while trying to open /dev/mmcblk0p1 Couldn't find valid filesystem superblock. root@OpenWrt:/# fdisk Disk /dev/mmcblk0: 3875 MB, 3875536896 bytes 235 heads, 20 sectors/track, 1610 cylinders Units = cylinders of 4700 * 512 = 2406400 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 11610 3781632 6 FAT16 How may I mount this partition? -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Mount mmc block
Hi, I'm trying to mount a emmc block on /mnt/mmc on a Ralink MT7628 board: root@OpenWrt:/# ls /dev/mmcblk0p1 /dev/mmcblk0p1 root@OpenWrt:/# ls /mnt/mmc/ root@OpenWrt:/# mount -t -ext3 /dev/mmcblk0p1 /mnt/mmc/ mount: mounting /dev/mmcblk0p1 on /mnt/mmc/ failed: No such device Am I missing something here? /mnt/mmc and /dev/mmcblk0p1 both exist. Regards, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] getaddrinfo breaks with IPV6 and IPV4
2015-08-06 12:02 GMT+02:00 Cristian Morales Vega :
> On 6 August 2015 at 10:52, Baptiste Clenet wrote:
>> Hi,
>>
>> I try to use getaddrinfo() function and I send as parameters:
>>
>> static char addrstr[256] = "::1";
>> struct addrinfo *res, *ainfo;
>> struct addrinfo hints;
>> memset ((char *)&hints, 0, sizeof(hints));
>> hints.ai_socktype = SOCK_DGRAM;
>> hints.ai_family = AF_UNSPEC;
>>
>> int error = getaddrinfo(addrstr, "", &hints, &res);
>>
>> if (error != 0) {
>> fprintf(stderr, "getaddrinfo: %s\n", gai_strerror(error));
>> return error;
>> }
>>
>>
>> And it gives me:
>> getaddrinfo: Unrecognized service
>>
>> I tried with an IPV4 address, same problem. Do you know which
>> implementation of getaddrinfo OpenWRT use?
>
> Why should it recognize the "" service? Give it the service you want
> to use, or NULL.
Yes, I've just found it as well, it was the reason, thanks anyway.
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] getaddrinfo breaks with IPV6 and IPV4
2015-08-06 11:52 GMT+02:00 Baptiste Clenet :
> Hi,
>
> I try to use getaddrinfo() function and I send as parameters:
>
> static char addrstr[256] = "::1";
> struct addrinfo *res, *ainfo;
> struct addrinfo hints;
> memset ((char *)&hints, 0, sizeof(hints));
> hints.ai_socktype = SOCK_DGRAM;
> hints.ai_family = AF_UNSPEC;
>
> int error = getaddrinfo(addrstr, "", &hints, &res);
Found my error, change "" to NULL make the deal! getaadrinfo can't
read "" service.
>
> if (error != 0) {
> fprintf(stderr, "getaddrinfo: %s\n", gai_strerror(error));
> return error;
> }
>
>
> And it gives me:
> getaddrinfo: Unrecognized service
>
> I tried with an IPV4 address, same problem. Do you know which
> implementation of getaddrinfo OpenWRT use?
>
> Regards,
>
> --
> Baptiste
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] getaddrinfo breaks with IPV6 and IPV4
Hi,
I try to use getaddrinfo() function and I send as parameters:
static char addrstr[256] = "::1";
struct addrinfo *res, *ainfo;
struct addrinfo hints;
memset ((char *)&hints, 0, sizeof(hints));
hints.ai_socktype = SOCK_DGRAM;
hints.ai_family = AF_UNSPEC;
int error = getaddrinfo(addrstr, "", &hints, &res);
if (error != 0) {
fprintf(stderr, "getaddrinfo: %s\n", gai_strerror(error));
return error;
}
And it gives me:
getaddrinfo: Unrecognized service
I tried with an IPV4 address, same problem. Do you know which
implementation of getaddrinfo OpenWRT use?
Regards,
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] package libcoap for OpenWRT, Makefile
2015-08-05 14:58 GMT+02:00 Yousong Zhou : > On 5 August 2015 at 16:09, Baptiste Clenet wrote: >> >> define Build/Compile >> $(MAKE) -C $(PKG_BUILD_DIR) \ >> $(TARGET_CONFIGURE_OPTS) \ >> CFLAGS="$(TARGET_CFLAGS) -I$(PKG_BUILD_DIR)" \ >> CPPFLAGS="$(TARGET_CPPFLAGS) -I$(PKG_BUILD_DIR)" \ >> LDFLAGS="$(TARGET_LDFLAGS) -L$(PKG_BUILD_DIR) -lcoap" >> endef >> > > Ahh, this should be the cause. Just dropping this section then the > package should compile. > > yousong Yes it was, thanks! Could give details why it didn't work then? If I am right, the compilation is done by libcoap itself so we don't need Build/Compile? It's not totally clear for me. -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] package libcoap for OpenWRT, Makefile
2015-08-05 12:57 GMT+02:00 Dirk Neukirchen : > On 05.08.2015 10:09, Baptiste Clenet wrote: >> Hi, >> >> I'm trying to add a package for libcoap and then compile it with my >> target Ralink MT7628. >> >> Here is the Makefile: >> # > >> >> coap_address_t is defined in address.h inside some #ifdef (#ifdef >> WITH_LWIP or #ifdef WITH_CONTIKI or #ifdef WITH_POSIX) >> >> I don't know if WITH_POSIX is defined. >> >> Regards, >> > > - You can check for WITH_POSIX (or other CFLAGS etc. in config.log Check it and it is defined. > - configure always sets -DWITH_POSIX in CPPFLAGS (see configure.in) Yes, it is set also. Don't know where the problem comes from. It works well with older version of libcoap. Other ideas? > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] package libcoap for OpenWRT, Makefile
Hi,
I'm trying to add a package for libcoap and then compile it with my
target Ralink MT7628.
Here is the Makefile:
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
include $(TOPDIR)/rules.mk
PKG_NAME:=libcoap
PKG_VERSION:=4.1.1
PKG_RELEASE:=1
PKG_SOURCE:=libcoap-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/libcoap
PKG_BUILD_DIR:=$(BUILD_DIR)/libcoap-$(PKG_VERSION)
PKG_INSTALL:=1
include $(INCLUDE_DIR)/package.mk
define Package/libcoap
SECTION:=libs
CATEGORY:=Libraries
DEPENDS:=
TITLE:=CoAP static library and example utilities
URL:=http://libcoap.sourceforge.net/
endef
define Build/Compile
$(MAKE) -C $(PKG_BUILD_DIR) \
$(TARGET_CONFIGURE_OPTS) \
CFLAGS="$(TARGET_CFLAGS) -I$(PKG_BUILD_DIR)" \
CPPFLAGS="$(TARGET_CPPFLAGS) -I$(PKG_BUILD_DIR)" \
LDFLAGS="$(TARGET_LDFLAGS) -L$(PKG_BUILD_DIR) -lcoap"
endef
define Build/Install
endef
define Build/InstallDev
$(INSTALL_DIR) $(1)/usr/include
$(CP) $(PKG_BUILD_DIR)/coap.h $(1)/usr/include/
$(INSTALL_DIR) $(1)/usr/lib
$(CP) $(PKG_BUILD_DIR)/libcoap.a $(1)/usr/lib/
endef
define Package/libcoap/install
$(INSTALL_DIR) $(1)/usr/bin
$(INSTALL_BIN) $(PKG_BUILD_DIR)/examples/coap-server $(1)/usr/bin/
$(INSTALL_BIN) $(PKG_BUILD_DIR)/examples/coap-client $(1)/usr/bin/
endef
$(eval $(call BuildPackage,libcoap))
I'm getting those errors with make V=s :
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating doc/Doxyfile
config.status: creating examples/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
configure: WARNING: unrecognized options: --disable-nls
// long make lines...
In file included from net.h:44:0,
from async.h:19,
from net.c:41:
address.h:134:19: error: unknown type name 'coap_address_t'
coap_address_init(coap_address_t *addr) {
^
address.h:149:1: error: unknown type name 'coap_address_t'
coap_address_equals(const coap_address_t *a, const coap_address_t *b) {
^
address.h:149:1: error: unknown type name 'coap_address_t'
address.h:159:1: error: unknown type name 'coap_address_t'
coap_is_mcast(const coap_address_t *a) {
^
In file included from net.h:47:0,
from async.h:19,
from net.c:41:
coap_time.h: In function 'coap_clock_init_impl':
coap_time.h:111:3: error: 'clock_offset' undeclared (first use in this function)
clock_offset = time(NULL);
^
coap_time.h:111:3: note: each undeclared identifier is reported only
once for each function it appears in
coap_time.h: At top level:
coap_time.h:126:17: error: unknown type name 'coap_tick_t'
coap_ticks_impl(coap_tick_t *t) {
^
coap_time.h:144:18: error: unknown type name 'coap_tick_t'
int coap_time_lt(coap_tick_t a, coap_tick_t b) {
^
coap_time.h:144:33: error: unknown type name 'coap_tick_t'
int coap_time_lt(coap_tick_t a, coap_tick_t b) {
^
coap_time.h:153:18: error: unknown type name 'coap_tick_t'
int coap_time_le(coap_tick_t a, coap_tick_t b) {
^
coap_time.h:153:33: error: unknown type name 'coap_tick_t'
int coap_time_le(coap_tick_t a, coap_tick_t b) {
^
In file included from async.h:19:0,
from net.c:41:
net.h:54:3: error: unknown type name 'coap_tick_t'
coap_tick_t t; /**< when to send PDU for the next time */
^
net.h:58:3: error: unknown type name 'coap_address_t'
coap_address_t local; /**< local address */
^
net.h:59:3: error: unknown type name 'coap_address_t'
coap_address_t remote; /**< remote address */
^
net.h:85:6: error: unknown type name 'coap_address_t'
const coap_address_t *remote,
^
net.h:109:3: error: unknown type name 'coap_tick_t'
coap_tick_t sendqueue_basetime;
^
In file included from async.h:19:0,
from net.c:41:
net.h:177:56: error: unknown type name 'coap_tick_t'
unsigned int coap_adjust_basetime(coap_context_t *ctx, coap_tick_t now);
^
net.h:186:1: error: unknown type name 'coap_address_t'
coap_context_t *coap_new_context(const coap_address_t *listen_addr);
^
net.h:220:11: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:254:8: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:276:7: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:293:10: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:309:5: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:326:8: error: unknown type name 'coap_address_t'
const coap_address_t *dst,
^
net.h:349:1: error: unknown type name 'coap_address_t'
void coap_transaction_id(const coap_address_t *peer, const coap_pdu_t *pdu,
^
net.h
Re: [OpenWrt-Devel] Change Uboot default values
>W dniu 22.07.2015 o 13:37, Baptiste Clenet pisze: > > I would like to change the default values of Uboot when I choose 2 in the > menu. > In the below example, I would like to change <1>, <2> and <3> by > defaults values that I would have set earlier. > > 2: System Load Linux Kernel then write to Flash via TFTP. > Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) > Please Input new ones /or Ctrl-C to discard > Input device IP (10.10.10.123) ==: <1> > Input server IP (10.10.10.3) ==: <2> > Input Linux Kernel filename () ==:<3> >It is usually stored on separate partition on flash. Read about UBoot >environment variables >athttp://www.denx.de/wiki/view/DULG/UBootEnvVariables - >in particular |**||*ipaddr, *||*|*serverip*|, >*||*bootfile and commands >setenv, saveenv.*| Thanks, works perfectly! 2015-07-22 14:18 GMT+02:00 Baptiste Clenet : > 2015-07-22 13:54 GMT+02:00 Yousong Zhou : >> On 22 July 2015 at 19:37, Baptiste Clenet wrote: >>> Hi, >>> >>> I would like to change the default values of Uboot when I choose 2 in the >>> menu. >>> In the below example, I would like to change <1>, <2> and <3> by >>> defaults values that I would have set earlier. >>> >> >> Looks like it's most likely hardcoded [1]. >> >> [1] >> https://github.com/8devices/u-boot/blob/a4ac3be49389f0801cae4c37454e59679d56f036/lib_mips/board.c#L1502 >> > > Yeah, but how to change the value then, I don't mind to hardcode them, > it's to flash quicker (not enter each time the values). > I changed it on one board but I don't remember how I have done that. > >> >> yousong >> >>> Example: >>> >>> Please choose the operation: >>>1: Load system code to SDRAM via TFTP. >>>2: Load system code then write to Flash via TFTP. >>>3: Boot system code via Flash (default). >>>4: Entr boot command line interface. >>>7: Load Boot Loader code then write to Flash via Serial. >>>9: Load Boot Loader code then write to Flash via TFTP. >>> >>> You choosed 2 >>> >>> 2: System Load Linux Kernel then write to Flash via TFTP. >>> Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) >>> Please Input new ones /or Ctrl-C to discard >>> Input device IP (10.10.10.123) ==: <1> >>> Input server IP (10.10.10.3) ==: <2> >>> Input Linux Kernel filename () ==:<3> >>> >>> Cheers, >>> >>> -- >>> Baptiste >>> ___ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > > > -- > Baptiste -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Change Uboot default values
2015-07-22 13:54 GMT+02:00 Yousong Zhou : > On 22 July 2015 at 19:37, Baptiste Clenet wrote: >> Hi, >> >> I would like to change the default values of Uboot when I choose 2 in the >> menu. >> In the below example, I would like to change <1>, <2> and <3> by >> defaults values that I would have set earlier. >> > > Looks like it's most likely hardcoded [1]. > > [1] > https://github.com/8devices/u-boot/blob/a4ac3be49389f0801cae4c37454e59679d56f036/lib_mips/board.c#L1502 > Yeah, but how to change the value then, I don't mind to hardcode them, it's to flash quicker (not enter each time the values). I changed it on one board but I don't remember how I have done that. > > yousong > >> Example: >> >> Please choose the operation: >>1: Load system code to SDRAM via TFTP. >>2: Load system code then write to Flash via TFTP. >>3: Boot system code via Flash (default). >>4: Entr boot command line interface. >>7: Load Boot Loader code then write to Flash via Serial. >>9: Load Boot Loader code then write to Flash via TFTP. >> >> You choosed 2 >> >> 2: System Load Linux Kernel then write to Flash via TFTP. >> Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) >> Please Input new ones /or Ctrl-C to discard >> Input device IP (10.10.10.123) ==: <1> >> Input server IP (10.10.10.3) ==: <2> >> Input Linux Kernel filename () ==:<3> >> >> Cheers, >> >> -- >> Baptiste >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Change Uboot default values
Hi, I would like to change the default values of Uboot when I choose 2 in the menu. In the below example, I would like to change <1>, <2> and <3> by defaults values that I would have set earlier. Example: Please choose the operation: 1: Load system code to SDRAM via TFTP. 2: Load system code then write to Flash via TFTP. 3: Boot system code via Flash (default). 4: Entr boot command line interface. 7: Load Boot Loader code then write to Flash via Serial. 9: Load Boot Loader code then write to Flash via TFTP. You choosed 2 2: System Load Linux Kernel then write to Flash via TFTP. Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Please Input new ones /or Ctrl-C to discard Input device IP (10.10.10.123) ==: <1> Input server IP (10.10.10.3) ==: <2> Input Linux Kernel filename () ==:<3> Cheers, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] ping6 messages do not go through all layers in the network stack
Hi, I'm using OpenWRT CHAOS CALMER (Bleeding Edge, r46141) with a Ralink MT7628 Board and Linux 4.1.0. I have set up a new interface: iwpan dev wpan0 set pan_id 0xbeef ip link set wpan0 up ip link add link wpan0 name lowpan0 type lowpan ip link set lowpan0 up Here is the settings: root@OpenWrt:/# ifconfig lowpan0 Link encap:UNSPEC HWaddr 05-38-09-06-90-E0-5E-3E-00-00-00-00-00-00-00-00 inet6 addr: fe80::738:906:90e0:5e3e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wpan0 Link encap:UNSPEC HWaddr 05-38-09-06-90-E0-5E-3E-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING NOARP MTU:127 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:300 RX bytes:0 (0.0 B) TX bytes:75 (75.0 B) root@OpenWrt:/# ip link 6: wpan0: mtu 127 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 300 link/ieee802.15.4 ef:57:b2:a9:2f:4e:90:76 brd ff:ff:ff:ff:ff:ff:ff:ff 7: lowpan0@NONE: mtu 1280 qdisc noqueue state UNKNOWN mode DEFAULT group default link/[825] ef:57:b2:a9:2f:4e:90:76 brd ff:ff:ff:ff:ff:ff:ff:ff root@OpenWrt:/# iwpan phy wpan_phy phy0 supported channels: page 0: 0,1,2,3,4,5,6,7,8,9,10 page 2: 0,1,2,3,4,5,6,7,8,9,10 current_page: 0 current_channel: 5 cca_mode: 1 tx_power: 0 root@OpenWrt:/# iwpan dev phy#0 Interface wpan0 ifindex 6 wpan_dev 0x1 extended_addr 0xef57b2a92f4e9076 short_addr 0x pan_id 0xbeef type node max_frame_retries -1 min_be 3 max_be 5 max_csma_backoffs 4 lbt 0 Then I try to ping6 another board using the lowpan0 interface: ping6 -I lowpan0 fe80::a8af:ac69:e53e:c7f1 All packets fail but more than that ifconfig tells me that no packet have been sent: root@OpenWrt:/# ifconfig lowpan0 Link encap:UNSPEC RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wpan0 Link encap:UNSPEC ... RX bytes:0 (0.0 B) TX bytes:75 (75.0 B) (--> this is when I set up lowpan0) In the ip link command, I'm wondering why I've got [825] for the lowpan0 interface? Why those packets are not transmitted over all the layers? Let me know if you need more info. -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] gpio-ralink, no interrupt GPIO pin?
Hi, I was trying to set an interrupt pin for my transceiver in the .dts and after some research, I had a look at gpio-ralink.c and found that the registers for interrupt GPIO are not used. (GINT_REDGE, GINT_FEDGE, GINT_HLVL ... for Ralink MT7628) How may I set a GPIO pin as an interrupt then? Regards, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Where is the maximum binary size defined for each board?
2015-06-30 20:07 GMT+02:00 N.Leiten : > Hi, > > It is selected in target//image/Makefile. > Actually there's many rules for each target, so, probably you need to write > own > rule for own target there. > > In email dated Вторник - 30 июня 2015 19:57:44 user Baptiste Clenet wrote: >> Hi, >> >> By slecting a board in menuconfig, OpenWRT sets a maximum binary size >> for this specific board. Where is this maximum defined? >> Since I don't use the default flash, the maximum size is bigger. >> >> Regards, >> >> > Thank you for the quick answer, I found what I needed. -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Where is the maximum binary size defined for each board?
Hi, By slecting a board in menuconfig, OpenWRT sets a maximum binary size for this specific board. Where is this maximum defined? Since I don't use the default flash, the maximum size is bigger. Regards, -- Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] m25p80: change en25q64 to w25q128
2015-06-30 15:56 GMT+02:00 Rafał Miłecki :
> On 30 June 2015 at 14:49, Baptiste Clenet wrote:
>> I assume that if the size of the binary is too big, OpenWRT doesn't
>> create sysupgrade.bin file.
>> I've seen that the en25q64 is the default flash memory for the Ralink
>> MT7628 board. I'm using the w25q128 instead so I change this in the
>> dts:
>> m25p80@0 {
>> #address-cells = <1>;
>> #size-cells = <1>;
>> compatible = "w25q128";
>> reg = <0 0>;
>> linux,modalias = "m25p80", "w25q128";
>> spi-max-frequency = <1000>;
>> m25p,chunked-io = <32>;
>>
>> Is that enough for OpenWRT to understand that my memory is twice
>> bigger? Because it still seems that it thinks my memory is only
>> 8MBytes instead of 16 so the binary is not created
>
> OpenWrt image building system doesn't use DTS as source of hardware info
Ok so why can't the image (squashfs) be more than 4MBytes?
Or where could I configure it?
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] m25p80: change en25q64 to w25q128
Hi,
I assume that if the size of the binary is too big, OpenWRT doesn't
create sysupgrade.bin file.
I've seen that the en25q64 is the default flash memory for the Ralink
MT7628 board. I'm using the w25q128 instead so I change this in the
dts:
m25p80@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "w25q128";
reg = <0 0>;
linux,modalias = "m25p80", "w25q128";
spi-max-frequency = <1000>;
m25p,chunked-io = <32>;
Is that enough for OpenWRT to understand that my memory is twice
bigger? Because it still seems that it thinks my memory is only
8MBytes instead of 16 so the binary is not created
Cheers,
--
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] jffs2 CRC failed (many times after reboot) - Ralink MT7628
2015-06-17 13:09 GMT+02:00 Baptiste Clenet : > > 2015-06-15 10:08 GMT+02:00 Baptiste Clenet : > >> Hello, >> >> The first boot, after flashing a new image, runs fine. >> I edit my /etc/config/network configuration then reboot and I get >> those errors (every reboot): >> >> [8.13] jffs2: jffs2_scan_inode_node(): CRC failed on node at >> 0x0046000c: Read 0x, calculated 0x4900568b >> ... >> ... (many times) >> ... >> [ 15.41] jffs2: notice: (306) jffs2_build_xattr_subsystem: >> complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) >> and 0 of xref (0 dead, 0 orphan) found. >> >> The flash driver seems to not work correctly after reboot. >> Any ideas? >> >> >> Baptiste >> > > This not just for /etc/config/network, any files or folder created is > deleted after reboot. How is this handle by openwrt/linux? > > Baptiste > Could anyone provide me the email address of someone that I could contact to help me on this problem? Cheers, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] jffs2 CRC failed (many times after reboot) - Ralink MT7628
2015-06-15 10:08 GMT+02:00 Baptiste Clenet : > Hello, > > The first boot, after flashing a new image, runs fine. > I edit my /etc/config/network configuration then reboot and I get > those errors (every reboot): > > [8.13] jffs2: jffs2_scan_inode_node(): CRC failed on node at > 0x0046000c: Read 0x, calculated 0x4900568b > ... > ... (many times) > ... > [ 15.41] jffs2: notice: (306) jffs2_build_xattr_subsystem: > complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) > and 0 of xref (0 dead, 0 orphan) found. > > The flash driver seems to not work correctly after reboot. > Any ideas? > > > Baptiste > This not just for /etc/config/network, any files or folder created is deleted after reboot. How is this handle by openwrt/linux? Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] jffs2 CRC failed (many times after reboot) - Ralink MT7628
Hello, The first boot, after flashing a new image, runs fine. I edit my /etc/config/network configuration then reboot and I get those errors (every reboot): [8.13] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x0046000c: Read 0x, calculated 0x4900568b ... ... (many times) ... [ 15.41] jffs2: notice: (306) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. The flash driver seems to not work correctly after reboot. Any ideas? Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Ralink MT76228 port to Linux 4.0, set new IP address fail
2015-06-12 11:12 GMT+02:00 Baptiste Clenet :
> 2015-06-11 16:31 GMT+02:00 Roman Yeryomin :
>> On 11 June 2015 at 16:36, Baptiste Clenet wrote:
>>> Hi,
>>>
>>> I've edited patches from Linux 3.18 to make the MT7628 work with Linux 4.0.
>>> OpenWRT launches, I have access to the shell.
>>> Next step, I configure the IP address with /etc/config/network and
>>> /etc/init.d/network reload. Ifconfig shows me my new address IP.
>>>
>>> But, I can't connect via ssh to my board and if I reboot the board, I
>>> get errors at boot:
>>> [ 10.23] jffs2: jffs2_scan_inode_node(): CRC failed on node at
>>> 0x004725bc: Read 0x, calculated 0x149094b5
>>> I would say it appears one hundred times with different calculated CRC.
>>> and finally the last line is:
>>> [ 11.00] jffs2: notice: (305) jffs2_build_xattr_subsystem:
>>> complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan)
>>> and 0 of xref (0 dead, 0 orphan) found.
>>>
>>>
>>> Then, I'm able to access to the shell but I still can't connect via
>>> ssh. The board constantly reports:
>>>
>>> [ 2410.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out
>>> [ 2410.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055
>>> [ 2410.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0,
>>> base=00dce000, max=128, ctx=126, dtx=126, fdx=123
>>> [ 2410.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0,
>>> base=01a36000, max=128, calc=121, drx=54
>>> [ 2415.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out
>>> [ 2415.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055
>>> [ 2415.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0,
>>> base=00dce000, max=128, ctx=126, dtx=126, fdx=123
>>> [ 2415.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0,
>>> base=01a36000, max=128, calc=121, drx=60
>>>
>>> It seems to be related to ethernet driver. Does anyone know those errors?
>>>
>>
>> I have the "transmit queue time out" error on ar71xx with 4.0.5 also.
>> Situation is very similar because ralink and ar71xx ethernet drivers
>> are maintained in OpenWrt only.
>> I believe it is related to recent timer/clock changes in kernel (in
>> 3.19 AFAIK). But I don't know neither timers nor network Linux stack
>> so well to tell what/where is the problem exactly.
>>
>> If somebody with more experience could point to a possible place to
>> look at that would be awesome.
>>
>>
>> Regards,
>> Roman
>
> Ok, let's see if someone can bring his knowledge on those parts and help us.
> Thanks
>
> Baptiste
I'm adding some details about the bug. after reloading
/etc/init.d/network (with an IP modified), WATCHDOG raises an error:
root@OpenWrt:/# [ 6426.01] [ cut here ]
[ 6426.01] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303
dev_watchdog+0x1d8/0x25c()
[ 6426.03] NETDEV WATCHDOG: eth0 (ralink_soc_eth): transmit queue
0 timed out
[ 6426.05] Modules linked in: pppoe ppp_async iptable_nat pppox
ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT
ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_recent xt_nat
xt_multiport xt_mark xt_mac xt_limit xt_id xt_helper xt_conntrack
xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT
xt_LOG xt_CT spidev slhc rfcomm nf_reject_ipv4 nf_nat_redirect
nf_nat_masquerade_ipv4 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6
nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_ftp iptable_raw
iptable_mangle iptable_filter ip_tables hidp hci_uart btusb bnep
bluetooth mac802154 crc_ccitt aead ieee802154_socket ieee802154
act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32
cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress 6lowpan hid
evdev input_core i2c_ralink i2c_dev ledtrig_usbdev ip6t_REJECT
nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle
ip6table_filter ip6_tables x_tables regmap_spi regmap_i2c i2c_core
regmap_core lzo_decompress lzo_compress ipv6 ecb crypto_blkcipher
leds_gpio ohci_platform ohci_hcd ehci_platform ehci_hcd
gpio_button_hotplug usbcore nls_base usb_common crc16 crypto_hash
[ 6426.25] CPU: 0 PID: 0 Comm: swapper Not tainted 4.0.4 #1
[ 6426.26] Stack : 0001 802b86a4
80311de3 8035342c
80312148 00f9 0002 0001 0004 80049318
0003 802bd644
012f 00f9 802bbc48 8030dc6c 0004 8004785c
0006 80fa5240
000
Re: [OpenWrt-Devel] Ralink MT76228 port to Linux 4.0, set new IP address fail
2015-06-12 18:02 GMT+02:00 Roman Yeryomin :
> On 12 June 2015 at 14:30, Baptiste Clenet wrote:
>> 2015-06-12 11:12 GMT+02:00 Baptiste Clenet :
>>> 2015-06-11 16:31 GMT+02:00 Roman Yeryomin :
>>>> On 11 June 2015 at 16:36, Baptiste Clenet wrote:
>>>>> Hi,
>>>>>
>>>>> I've edited patches from Linux 3.18 to make the MT7628 work with Linux
>>>>> 4.0.
>>>>> OpenWRT launches, I have access to the shell.
>>>>> Next step, I configure the IP address with /etc/config/network and
>>>>> /etc/init.d/network reload. Ifconfig shows me my new address IP.
>>>>>
>>>>> But, I can't connect via ssh to my board and if I reboot the board, I
>>>>> get errors at boot:
>>>>> [ 10.23] jffs2: jffs2_scan_inode_node(): CRC failed on node at
>>>>> 0x004725bc: Read 0x, calculated 0x149094b5
>>>>> I would say it appears one hundred times with different calculated CRC.
>>>>> and finally the last line is:
>>>>> [ 11.00] jffs2: notice: (305) jffs2_build_xattr_subsystem:
>>>>> complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan)
>>>>> and 0 of xref (0 dead, 0 orphan) found.
>>>>>
>>>>>
>>>>> Then, I'm able to access to the shell but I still can't connect via
>>>>> ssh. The board constantly reports:
>>>>>
>>>>> [ 2410.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out
>>>>> [ 2410.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055
>>>>> [ 2410.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0,
>>>>> base=00dce000, max=128, ctx=126, dtx=126, fdx=123
>>>>> [ 2410.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0,
>>>>> base=01a36000, max=128, calc=121, drx=54
>>>>> [ 2415.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out
>>>>> [ 2415.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055
>>>>> [ 2415.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0,
>>>>> base=00dce000, max=128, ctx=126, dtx=126, fdx=123
>>>>> [ 2415.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0,
>>>>> base=01a36000, max=128, calc=121, drx=60
>>>>>
>>>>> It seems to be related to ethernet driver. Does anyone know those errors?
>>>>>
>>>>
>>>> I have the "transmit queue time out" error on ar71xx with 4.0.5 also.
>>>> Situation is very similar because ralink and ar71xx ethernet drivers
>>>> are maintained in OpenWrt only.
>>>> I believe it is related to recent timer/clock changes in kernel (in
>>>> 3.19 AFAIK). But I don't know neither timers nor network Linux stack
>>>> so well to tell what/where is the problem exactly.
>>>>
>>>> If somebody with more experience could point to a possible place to
>>>> look at that would be awesome.
>>>>
>>>>
>>>> Regards,
>>>> Roman
>>>
>>> Ok, let's see if someone can bring his knowledge on those parts and help us.
>>> Thanks
>>>
>>> Baptiste
>>
>>
>> I'm adding some details about the bug. after reloading
>> /etc/init.d/network (with an IP modified), WATCHDOG raises an error:
>>
>> root@OpenWrt:/# [ 6426.01] [ cut here ]
>> [ 6426.01] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303
>> dev_watchdog+0x1d8/0x25c()
>> [ 6426.03] NETDEV WATCHDOG: eth0 (ralink_soc_eth): transmit queue
>> 0 timed out
>
> yes, exactly the same issue here with ar71xx:
> http://p.tet.rtu.lv/pbzn5sspm/wvtsep/raw
Watchdog problem solved thanks to Mingyu Li.
Patch the file ralink_soc_eth.c
@@ -983,8 +983,11 @@ static int fe_poll(struct napi_struct *napi, int budget)
if (!tx_again && (rx_done < budget)) {
status = fe_reg_r32(FE_REG_FE_INT_STATUS);
- if (status & (tx_intr | rx_intr ))
+ if (status & (tx_intr | rx_intr )) {
+ /* let napi poll again */
+ rx_done = budget;
goto poll_again;
+ }
napi_complete(napi);
This solution is related to the ralink board only.
Last problem is:
[8.13] jffs2: jffs2_scan_inode_node(): CRC failed on node at
0x0046000c: Read 0x, calculated 0x4900568b
...
... (many times)
...
[ 15.41] jffs2: notice: (306) jffs2_build_xattr_subsystem:
The flash driver seems to not work correctly after reboot.
Any ideas on that?
Baptiste
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Ralink MT76228 port to Linux 4.0, set new IP address fail
2015-06-11 16:31 GMT+02:00 Roman Yeryomin : > On 11 June 2015 at 16:36, Baptiste Clenet wrote: >> Hi, >> >> I've edited patches from Linux 3.18 to make the MT7628 work with Linux 4.0. >> OpenWRT launches, I have access to the shell. >> Next step, I configure the IP address with /etc/config/network and >> /etc/init.d/network reload. Ifconfig shows me my new address IP. >> >> But, I can't connect via ssh to my board and if I reboot the board, I >> get errors at boot: >> [ 10.23] jffs2: jffs2_scan_inode_node(): CRC failed on node at >> 0x004725bc: Read 0x, calculated 0x149094b5 >> I would say it appears one hundred times with different calculated CRC. >> and finally the last line is: >> [ 11.00] jffs2: notice: (305) jffs2_build_xattr_subsystem: >> complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) >> and 0 of xref (0 dead, 0 orphan) found. >> >> >> Then, I'm able to access to the shell but I still can't connect via >> ssh. The board constantly reports: >> >> [ 2410.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out >> [ 2410.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055 >> [ 2410.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0, >> base=00dce000, max=128, ctx=126, dtx=126, fdx=123 >> [ 2410.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0, >> base=01a36000, max=128, calc=121, drx=54 >> [ 2415.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out >> [ 2415.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055 >> [ 2415.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0, >> base=00dce000, max=128, ctx=126, dtx=126, fdx=123 >> [ 2415.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0, >> base=01a36000, max=128, calc=121, drx=60 >> >> It seems to be related to ethernet driver. Does anyone know those errors? >> > > I have the "transmit queue time out" error on ar71xx with 4.0.5 also. > Situation is very similar because ralink and ar71xx ethernet drivers > are maintained in OpenWrt only. > I believe it is related to recent timer/clock changes in kernel (in > 3.19 AFAIK). But I don't know neither timers nor network Linux stack > so well to tell what/where is the problem exactly. > > If somebody with more experience could point to a possible place to > look at that would be awesome. > > > Regards, > Roman Ok, let's see if someone can bring his knowledge on those parts and help us. Thanks Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Ralink MT76228 port to Linux 4.0, set new IP address fail
Hi, I've edited patches from Linux 3.18 to make the MT7628 work with Linux 4.0. OpenWRT launches, I have access to the shell. Next step, I configure the IP address with /etc/config/network and /etc/init.d/network reload. Ifconfig shows me my new address IP. But, I can't connect via ssh to my board and if I reboot the board, I get errors at boot: [ 10.23] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x004725bc: Read 0x, calculated 0x149094b5 I would say it appears one hundred times with different calculated CRC. and finally the last line is: [ 11.00] jffs2: notice: (305) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. Then, I'm able to access to the shell but I still can't connect via ssh. The board constantly reports: [ 2410.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out [ 2410.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055 [ 2410.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0, base=00dce000, max=128, ctx=126, dtx=126, fdx=123 [ 2410.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0, base=01a36000, max=128, calc=121, drx=54 [ 2415.01] ralink_soc_eth 1010.ethernet eth0: transmit timed out [ 2415.02] ralink_soc_eth 1010.ethernet eth0: dma_cfg:0055 [ 2415.03] ralink_soc_eth 1010.ethernet eth0: tx_ring=0, base=00dce000, max=128, ctx=126, dtx=126, fdx=123 [ 2415.05] ralink_soc_eth 1010.ethernet eth0: rx_ring=0, base=01a36000, max=128, calc=121, drx=60 It seems to be related to ethernet driver. Does anyone know those errors? Regards, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-10 9:09 GMT+02:00 Varka Bhadram : > On 06/10/2015 12:35 PM, Baptiste Clenet wrote: > >> 2015-06-09 6:05 GMT+02:00 Varka Bhadram : >>> >>> On 06/08/2015 07:32 PM, Baptiste Clenet wrote: >>> >>>> 2015-06-08 15:23 GMT+02:00 Varka Bhadram : >>>>> >>>>> >>> (...) >>> >>>> Thanks Varka for your help! >>>> >>>> It compiles now without those module: >>>> - kmod-bluetooth >>>> - kmod-bluetooth_6lowpan >>>> - kmod-6lowpan >>>> - kmod-ieee802154 >>>> - kmod-ieee802154-6lowpan >>>> - kmod-ieee802154-drivers >>>> - kmod-mac802154 >>>> - kmod-wpan-at86rf230 >>>> - wpan-tools >>>> >>>> It's basically the same conf as yours. >>>> >>>> I don't get why those module would make an error since they worked >>>> well with Linux 3.18. >>>> >>>> Here are my tries: >>>> - kmod-6lowpan >>>> - kmod-ieee802154 >>>> - kmod-ieee802154-6lowpan >>>> - kmod-ieee802154-drivers >>> >>> >>> Have you added this ? >>> >>>> - kmod-mac802154 >>>> - kmod-wpan-at86rf230 >> >> Yes this packages weren't in OPENWRT Tree. I removed them and use the >> right ones now. >> - kmod-wpan-at86rf230 doesn't exist either, perhaps you meant >> kmod-at86rf230 under Wireless? > > > Yes.. :-) > >> I added: >> - kmod-at86rf230 >> - kmod-ieee802154 >> - kmod-mac802154 >> - kmod-ipv6 >> >> I got the following error: >> Package kmod-at86rf230 is missing dependencies for the following >> libraries: >> regmap-core.ko >> regmap-spi.ko > > > Try this patch: > > diff --git a/package/kernel/linux/modules/wpan.mk > b/package/kernel/linux/modules/wpan.mk > index 6b07809..412d70e 100644 > --- a/package/kernel/linux/modules/wpan.mk > +++ b/package/kernel/linux/modules/wpan.mk > @@ -71,7 +71,7 @@ $(eval $(call KernelPackage,fakelb)) > define KernelPackage/at86rf230 >SUBMENU:=$(WPAN_MENU) >TITLE:=AT86RF230 transceiver driver > - DEPENDS:=+kmod-mac802154 > + DEPENDS:=+kmod-mac802154 +kmod-regmap >KCONFIG:=CONFIG_IEEE802154_AT86RF230 \ > CONFIG_SPI=y \ > CONFIG_SPI_MASTER=y > @@ -107,7 +107,7 @@ $(eval $(call KernelPackage,cc2520)) > define KernelPackage/ieee802154_6lowpan >SUBMENU:=$(WPAN_MENU) >TITLE:= 6LoWPAN support over IEEE-802.15.4 > - DEPENDS:=@LINUX_4_0 +kmod-6lowpan > + DEPENDS:=@LINUX_4_0 +kmod-6lowpan +kmod-ieee802154 >KCONFIG:=CONFIG_IEEE802154_6LOWPAN >FILES:= \ > $(LINUX_DIR)/net/ieee802154/6lowpan/ieee802154_6lowpan.ko@ge4.0 \ > -- > 1.7.9.5 > > -- > Varka Bhadram > Thanks Varka, works well now! Next step is making at86rf230 work seamlessly. Cheers, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-09 6:05 GMT+02:00 Varka Bhadram : > On 06/08/2015 07:32 PM, Baptiste Clenet wrote: > >> 2015-06-08 15:23 GMT+02:00 Varka Bhadram : >>> >>> > (...) > >> >> Thanks Varka for your help! >> >> It compiles now without those module: >> - kmod-bluetooth >> - kmod-bluetooth_6lowpan >> - kmod-6lowpan >> - kmod-ieee802154 >> - kmod-ieee802154-6lowpan >> - kmod-ieee802154-drivers >> - kmod-mac802154 >> - kmod-wpan-at86rf230 >> - wpan-tools >> >> It's basically the same conf as yours. >> >> I don't get why those module would make an error since they worked >> well with Linux 3.18. >> >> Here are my tries: >> - kmod-6lowpan >> - kmod-ieee802154 >> - kmod-ieee802154-6lowpan >> - kmod-ieee802154-drivers > > > Have you added this ? > >> - kmod-mac802154 >> - kmod-wpan-at86rf230 > Yes this packages weren't in OPENWRT Tree. I removed them and use the right ones now. - kmod-wpan-at86rf230 doesn't exist either, perhaps you meant kmod-at86rf230 under Wireless? I added: - kmod-at86rf230 - kmod-ieee802154 - kmod-mac802154 - kmod-ipv6 I got the following error: Package kmod-at86rf230 is missing dependencies for the following libraries: regmap-core.ko regmap-spi.ko Same error if I add kmod-regmap (which should add those missing libraries, shouldn't it?) Baptiste > > This also. > > I don't see these packages in OpenWrt tree. > Please use already existing package stuff... > > All these packages available in Kernel Modules -> Wireless Drivers > in your menuconfig. > > >> - wpan-tools >> --> ERROR: module >> >> '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/ieee802154/af_802154.ko' >> is missing. >> >> - kmod-bluetooth >> - kmod-bluetooth_6lowpan >> - kmod-6lowpan >> - kmod-ieee802154 >> - kmod-ieee802154-6lowpan >> - kmod-ieee802154-drivers >> - kmod-mac802154 >> - kmod-wpan-at86rf230 >> - wpan-tools >> --->ERROR: module >> >> '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' >> is missing. > > > -- > Varka Bhadram > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 16:02 GMT+02:00 Baptiste Clenet :
> 2015-06-08 15:23 GMT+02:00 Varka Bhadram :
>>
>> On Jun 8, 2015 6:41 PM, "Baptiste Clenet" wrote:
>>>
>>> 2015-06-08 14:46 GMT+02:00 Baptiste Clenet :
>>> > 2015-06-08 14:20 GMT+02:00 Varka Bhadram :
>>> >> On 06/08/2015 05:48 PM, Baptiste Clenet wrote:
>>> >>>
>>> >>> 2015-06-08 14:10 GMT+02:00 Varka Bhadram :
>>> >>>>
>>> >>>> On 06/08/2015 05:27 PM, Baptiste Clenet wrote:
>>> >>>>>
>>> >>>>> 2015-06-08 13:49 GMT+02:00 Baptiste Clenet :
>>> >>>>>>
>>> >>>>>> 2015-06-08 10:53 GMT+02:00 Varka Bhadram :
>>> >>>>>>>
>>> >>>>>>> On 06/08/2015 01:36 PM, Baptiste Clenet wrote:
>>> >>>>>>>
>>> >>>>>>>>>> I've edited variable KERNEL_PATCHVER:=3.18 to
>>> >>>>>>>>>> KERNEL_PATCHVER:=4.0.4
>>> >>>>>>>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4
>>> >>>>>>>>>> installed
>>> >>>>>>>>>
>>> >>>>>>>>>
>>> >>>>>>>>> Also you need to specify the configuration file for 4.0.4
>>> >>>>>>>>> kernel.
>>> >>>>>>>>>
>>> >>>>>>>>> just copy the file target/linux/ramips/mt7628/config-3.18 as
>>> >>>>>>>>> target/linux/ramips/mt7628/config-4.0
>>> >>>>>>>>>
>>> >>>>>>>>> I hope it will resolve this error.
>>> >>>>>>>>>
>>> >>>>>>>>> --
>>> >>>>>>>>> Varka Bhadram
>>> >>>>>>>>>
>>> >>>>>>>> Thanks Varka, I copied the files, I'm trying to make now. On
>>> >>>>>>>> question
>>> >>>>>>>> came up, what about patches? There are many patches for Linux
>>> >>>>>>>> 3.18,
>>> >>>>>>>> is
>>> >>>>>>>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains
>>> >>>>>>>> a
>>> >>>>>>>> folder for 3.18 patches.
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> There may be so-many patches merged into 4.0 from patches-3.18
>>> >>>>>>> directory..?
>>> >>>>>>>
>>> >>>>>>> I just created a directory with the name patches-4.0 under
>>> >>>>>>> target/linux/ramips/ .
>>> >>>>>>>
>>> >>>>>>> I think its a bad solution. But the build was successful and able
>>> >>>>>>> generate
>>> >>>>>>> the
>>> >>>>>>> binaries in bin/ramips directory. I don't know whether these
>>> >>>>>>> binaries
>>> >>>>>>> working
>>> >>>>>>> or not. I don't have hardware to test these binaries.
>>> >>>>>
>>> >>>>> Why is it a bad solution?
>>> >>>>>
>>> >>>>>>> I only copied one patch from patches-3.18 to 4.0 to fix one build
>>> >>>>>>> error.
>>> >>>>>>> i.e., 0103-MIPS-OWRTDTB.patch
>>> >>>>>>>
>>>
>>>
>>> "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/MT7628.dtb
>>> DTB marker not found!"
>>> Was it the error?
>>>
>>> I added 'trunk/target/linux/ramips/patches-4.0/0103-MIPS-OWRTDTB.patch'
>>> but it didn't solve the problem. Do I need to tell OPENWRT to use
>>> patches-4.0?
>>>
>> Try
>> make target/linux/{clean,prepare} V=s
>> make
>>
>>> Baptiste
>>>
>>> >>>>>>> Hope it helps. Its just a shoot in the dark for your problem.
>>> >>>>>>>
>>> >>>>>>> Test it and update the results.
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 15:23 GMT+02:00 Varka Bhadram :
>
> On Jun 8, 2015 6:41 PM, "Baptiste Clenet" wrote:
>>
>> 2015-06-08 14:46 GMT+02:00 Baptiste Clenet :
>> > 2015-06-08 14:20 GMT+02:00 Varka Bhadram :
>> >> On 06/08/2015 05:48 PM, Baptiste Clenet wrote:
>> >>>
>> >>> 2015-06-08 14:10 GMT+02:00 Varka Bhadram :
>> >>>>
>> >>>> On 06/08/2015 05:27 PM, Baptiste Clenet wrote:
>> >>>>>
>> >>>>> 2015-06-08 13:49 GMT+02:00 Baptiste Clenet :
>> >>>>>>
>> >>>>>> 2015-06-08 10:53 GMT+02:00 Varka Bhadram :
>> >>>>>>>
>> >>>>>>> On 06/08/2015 01:36 PM, Baptiste Clenet wrote:
>> >>>>>>>
>> >>>>>>>>>> I've edited variable KERNEL_PATCHVER:=3.18 to
>> >>>>>>>>>> KERNEL_PATCHVER:=4.0.4
>> >>>>>>>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4
>> >>>>>>>>>> installed
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Also you need to specify the configuration file for 4.0.4
>> >>>>>>>>> kernel.
>> >>>>>>>>>
>> >>>>>>>>> just copy the file target/linux/ramips/mt7628/config-3.18 as
>> >>>>>>>>> target/linux/ramips/mt7628/config-4.0
>> >>>>>>>>>
>> >>>>>>>>> I hope it will resolve this error.
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Varka Bhadram
>> >>>>>>>>>
>> >>>>>>>> Thanks Varka, I copied the files, I'm trying to make now. On
>> >>>>>>>> question
>> >>>>>>>> came up, what about patches? There are many patches for Linux
>> >>>>>>>> 3.18,
>> >>>>>>>> is
>> >>>>>>>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains
>> >>>>>>>> a
>> >>>>>>>> folder for 3.18 patches.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> There may be so-many patches merged into 4.0 from patches-3.18
>> >>>>>>> directory..?
>> >>>>>>>
>> >>>>>>> I just created a directory with the name patches-4.0 under
>> >>>>>>> target/linux/ramips/ .
>> >>>>>>>
>> >>>>>>> I think its a bad solution. But the build was successful and able
>> >>>>>>> generate
>> >>>>>>> the
>> >>>>>>> binaries in bin/ramips directory. I don't know whether these
>> >>>>>>> binaries
>> >>>>>>> working
>> >>>>>>> or not. I don't have hardware to test these binaries.
>> >>>>>
>> >>>>> Why is it a bad solution?
>> >>>>>
>> >>>>>>> I only copied one patch from patches-3.18 to 4.0 to fix one build
>> >>>>>>> error.
>> >>>>>>> i.e., 0103-MIPS-OWRTDTB.patch
>> >>>>>>>
>>
>>
>> "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/MT7628.dtb
>> DTB marker not found!"
>> Was it the error?
>>
>> I added 'trunk/target/linux/ramips/patches-4.0/0103-MIPS-OWRTDTB.patch'
>> but it didn't solve the problem. Do I need to tell OPENWRT to use
>> patches-4.0?
>>
> Try
> make target/linux/{clean,prepare} V=s
> make
>
>> Baptiste
>>
>> >>>>>>> Hope it helps. Its just a shoot in the dark for your problem.
>> >>>>>>>
>> >>>>>>> Test it and update the results.
>> >>>>>>>
>> >>>>>>> Thanks
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Varka Bhadram
>> >>>>>>>
>> >>>>>> Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error:
>> >>>>
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 14:46 GMT+02:00 Baptiste Clenet : > 2015-06-08 14:20 GMT+02:00 Varka Bhadram : >> On 06/08/2015 05:48 PM, Baptiste Clenet wrote: >>> >>> 2015-06-08 14:10 GMT+02:00 Varka Bhadram : >>>> >>>> On 06/08/2015 05:27 PM, Baptiste Clenet wrote: >>>>> >>>>> 2015-06-08 13:49 GMT+02:00 Baptiste Clenet : >>>>>> >>>>>> 2015-06-08 10:53 GMT+02:00 Varka Bhadram : >>>>>>> >>>>>>> On 06/08/2015 01:36 PM, Baptiste Clenet wrote: >>>>>>> >>>>>>>>>> I've edited variable KERNEL_PATCHVER:=3.18 to >>>>>>>>>> KERNEL_PATCHVER:=4.0.4 >>>>>>>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 >>>>>>>>>> installed >>>>>>>>> >>>>>>>>> >>>>>>>>> Also you need to specify the configuration file for 4.0.4 kernel. >>>>>>>>> >>>>>>>>> just copy the file target/linux/ramips/mt7628/config-3.18 as >>>>>>>>> target/linux/ramips/mt7628/config-4.0 >>>>>>>>> >>>>>>>>> I hope it will resolve this error. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Varka Bhadram >>>>>>>>> >>>>>>>> Thanks Varka, I copied the files, I'm trying to make now. On question >>>>>>>> came up, what about patches? There are many patches for Linux 3.18, >>>>>>>> is >>>>>>>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains a >>>>>>>> folder for 3.18 patches. >>>>>>> >>>>>>> >>>>>>> There may be so-many patches merged into 4.0 from patches-3.18 >>>>>>> directory..? >>>>>>> >>>>>>> I just created a directory with the name patches-4.0 under >>>>>>> target/linux/ramips/ . >>>>>>> >>>>>>> I think its a bad solution. But the build was successful and able >>>>>>> generate >>>>>>> the >>>>>>> binaries in bin/ramips directory. I don't know whether these binaries >>>>>>> working >>>>>>> or not. I don't have hardware to test these binaries. >>>>> >>>>> Why is it a bad solution? >>>>> >>>>>>> I only copied one patch from patches-3.18 to 4.0 to fix one build >>>>>>> error. >>>>>>> i.e., 0103-MIPS-OWRTDTB.patch >>>>>>> "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/MT7628.dtb DTB marker not found!" Was it the error? I added 'trunk/target/linux/ramips/patches-4.0/0103-MIPS-OWRTDTB.patch' but it didn't solve the problem. Do I need to tell OPENWRT to use patches-4.0? Baptiste >>>>>>> Hope it helps. Its just a shoot in the dark for your problem. >>>>>>> >>>>>>> Test it and update the results. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> -- >>>>>>> Varka Bhadram >>>>>>> >>>>>> Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error: >>>>>> >>>>>> WARNING: kmod-6lowpan-iphc is not available in the kernel config - >>>>>> generating empty package >>>>>> >>>>>> ... >>>>>> >>>>>> ERROR: module >>>>>> >>>>>> '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' >>>>>> is missing. >>>>>> >>>>>> This is about a package I added in menuconfig but I need them. Those >>>>>> package worked well while compiling with Linux 3.18. Any idea? >>>> >>>> >>>> What package did you add..? >>> >>> I added : >>> - kmod-bluetooth >>> - kmod-bluetooth_6lowpan >>> - kmod-6lowpan >>> - kmod-ieee802154 >>> - kmod-ieee802154-6lowpan >>> - kmod-ieee802154-drivers >>> - kmod-mac802154 >>> - kmod-wpan-at86rf230 >>> - iw >>> - wpan-tools >> >> >> These are already came into OpenWrt with [1]. >> >> [1]:https://lists.openwrt.org/pipermail/openwrt-devel/2015-April/032515.html >> >> -- >> Varka Bhadram >> > > Yes, I saw, I meant by added "set in menuconfig". > > You meant that with or without those module, it should work? > > Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 14:20 GMT+02:00 Varka Bhadram : > On 06/08/2015 05:48 PM, Baptiste Clenet wrote: >> >> 2015-06-08 14:10 GMT+02:00 Varka Bhadram : >>> >>> On 06/08/2015 05:27 PM, Baptiste Clenet wrote: >>>> >>>> 2015-06-08 13:49 GMT+02:00 Baptiste Clenet : >>>>> >>>>> 2015-06-08 10:53 GMT+02:00 Varka Bhadram : >>>>>> >>>>>> On 06/08/2015 01:36 PM, Baptiste Clenet wrote: >>>>>> >>>>>>>>> I've edited variable KERNEL_PATCHVER:=3.18 to >>>>>>>>> KERNEL_PATCHVER:=4.0.4 >>>>>>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 >>>>>>>>> installed >>>>>>>> >>>>>>>> >>>>>>>> Also you need to specify the configuration file for 4.0.4 kernel. >>>>>>>> >>>>>>>> just copy the file target/linux/ramips/mt7628/config-3.18 as >>>>>>>> target/linux/ramips/mt7628/config-4.0 >>>>>>>> >>>>>>>> I hope it will resolve this error. >>>>>>>> >>>>>>>> -- >>>>>>>> Varka Bhadram >>>>>>>> >>>>>>> Thanks Varka, I copied the files, I'm trying to make now. On question >>>>>>> came up, what about patches? There are many patches for Linux 3.18, >>>>>>> is >>>>>>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains a >>>>>>> folder for 3.18 patches. >>>>>> >>>>>> >>>>>> There may be so-many patches merged into 4.0 from patches-3.18 >>>>>> directory..? >>>>>> >>>>>> I just created a directory with the name patches-4.0 under >>>>>> target/linux/ramips/ . >>>>>> >>>>>> I think its a bad solution. But the build was successful and able >>>>>> generate >>>>>> the >>>>>> binaries in bin/ramips directory. I don't know whether these binaries >>>>>> working >>>>>> or not. I don't have hardware to test these binaries. >>>> >>>> Why is it a bad solution? >>>> >>>>>> I only copied one patch from patches-3.18 to 4.0 to fix one build >>>>>> error. >>>>>> i.e., 0103-MIPS-OWRTDTB.patch >>>>>> >>>>>> Hope it helps. Its just a shoot in the dark for your problem. >>>>>> >>>>>> Test it and update the results. >>>>>> >>>>>> Thanks >>>>>> >>>>>> -- >>>>>> Varka Bhadram >>>>>> >>>>> Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error: >>>>> >>>>> WARNING: kmod-6lowpan-iphc is not available in the kernel config - >>>>> generating empty package >>>>> >>>>> ... >>>>> >>>>> ERROR: module >>>>> >>>>> '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' >>>>> is missing. >>>>> >>>>> This is about a package I added in menuconfig but I need them. Those >>>>> package worked well while compiling with Linux 3.18. Any idea? >>> >>> >>> What package did you add..? >> >> I added : >> - kmod-bluetooth >> - kmod-bluetooth_6lowpan >> - kmod-6lowpan >> - kmod-ieee802154 >> - kmod-ieee802154-6lowpan >> - kmod-ieee802154-drivers >> - kmod-mac802154 >> - kmod-wpan-at86rf230 >> - iw >> - wpan-tools > > > These are already came into OpenWrt with [1]. > > [1]:https://lists.openwrt.org/pipermail/openwrt-devel/2015-April/032515.html > > -- > Varka Bhadram > Yes, I saw, I meant by added "set in menuconfig". You meant that with or without those module, it should work? Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 14:10 GMT+02:00 Varka Bhadram : > On 06/08/2015 05:27 PM, Baptiste Clenet wrote: >> >> 2015-06-08 13:49 GMT+02:00 Baptiste Clenet : >>> >>> 2015-06-08 10:53 GMT+02:00 Varka Bhadram : >>>> >>>> On 06/08/2015 01:36 PM, Baptiste Clenet wrote: >>>> >>>>>>> I've edited variable KERNEL_PATCHVER:=3.18 to KERNEL_PATCHVER:=4.0.4 >>>>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 installed >>>>>> >>>>>> >>>>>> Also you need to specify the configuration file for 4.0.4 kernel. >>>>>> >>>>>> just copy the file target/linux/ramips/mt7628/config-3.18 as >>>>>> target/linux/ramips/mt7628/config-4.0 >>>>>> >>>>>> I hope it will resolve this error. >>>>>> >>>>>> -- >>>>>> Varka Bhadram >>>>>> >>>>> Thanks Varka, I copied the files, I'm trying to make now. On question >>>>> came up, what about patches? There are many patches for Linux 3.18, is >>>>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains a >>>>> folder for 3.18 patches. >>>> >>>> >>>> There may be so-many patches merged into 4.0 from patches-3.18 >>>> directory..? >>>> >>>> I just created a directory with the name patches-4.0 under >>>> target/linux/ramips/ . >>>> >>>> I think its a bad solution. But the build was successful and able >>>> generate >>>> the >>>> binaries in bin/ramips directory. I don't know whether these binaries >>>> working >>>> or not. I don't have hardware to test these binaries. >> >> Why is it a bad solution? >> >>>> I only copied one patch from patches-3.18 to 4.0 to fix one build error. >>>> i.e., 0103-MIPS-OWRTDTB.patch >>>> >>>> Hope it helps. Its just a shoot in the dark for your problem. >>>> >>>> Test it and update the results. >>>> >>>> Thanks >>>> >>>> -- >>>> Varka Bhadram >>>> >>> Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error: >>> >>> WARNING: kmod-6lowpan-iphc is not available in the kernel config - >>> generating empty package >>> >>> ... >>> >>> ERROR: module >>> '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' >>> is missing. >>> >>> This is about a package I added in menuconfig but I need them. Those >>> package worked well while compiling with Linux 3.18. Any idea? > > > What package did you add..? I added : - kmod-bluetooth - kmod-bluetooth_6lowpan - kmod-6lowpan - kmod-ieee802154 - kmod-ieee802154-6lowpan - kmod-ieee802154-drivers - kmod-mac802154 - kmod-wpan-at86rf230 - iw - wpan-tools This conf worked with Linux 3.18. > > IEEE-802.15.4, 6LoWPAN and 6LoWPAN shared code b/w bluetooth and > IEEE-802.15.4 > packages supported by OpenWrt now. > >>> >>> Varka, which configuration did you use? Only the minimal? (I mean set >>> Target and Subtarget in menuconfig) > > > I just did the minimal configuration. > > -- > Varka Bhadram > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 13:49 GMT+02:00 Baptiste Clenet : > 2015-06-08 10:53 GMT+02:00 Varka Bhadram : >> On 06/08/2015 01:36 PM, Baptiste Clenet wrote: >> >>>>> >>>>> I've edited variable KERNEL_PATCHVER:=3.18 to KERNEL_PATCHVER:=4.0.4 >>>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 installed >>>> >>>> >>>> Also you need to specify the configuration file for 4.0.4 kernel. >>>> >>>> just copy the file target/linux/ramips/mt7628/config-3.18 as >>>> target/linux/ramips/mt7628/config-4.0 >>>> >>>> I hope it will resolve this error. >>>> >>>> -- >>>> Varka Bhadram >>>> >>> >>> Thanks Varka, I copied the files, I'm trying to make now. On question >>> came up, what about patches? There are many patches for Linux 3.18, is >>> there any for Linux 4.0? target/linux/ramips/mt7628 only contains a >>> folder for 3.18 patches. >> >> >> There may be so-many patches merged into 4.0 from patches-3.18 directory..? >> >> I just created a directory with the name patches-4.0 under >> target/linux/ramips/ . >> >> I think its a bad solution. But the build was successful and able generate >> the >> binaries in bin/ramips directory. I don't know whether these binaries >> working >> or not. I don't have hardware to test these binaries. Why is it a bad solution? >> >> I only copied one patch from patches-3.18 to 4.0 to fix one build error. >> i.e., 0103-MIPS-OWRTDTB.patch >> >> Hope it helps. Its just a shoot in the dark for your problem. >> >> Test it and update the results. >> >> Thanks >> >> -- >> Varka Bhadram >> > > Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error: > > WARNING: kmod-6lowpan-iphc is not available in the kernel config - > generating empty package > > ... > > ERROR: module > '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' > is missing. > > This is about a package I added in menuconfig but I need them. Those > package worked well while compiling with Linux 3.18. Any idea? > > Varka, which configuration did you use? Only the minimal? (I mean set > Target and Subtarget in menuconfig) > > Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 10:53 GMT+02:00 Varka Bhadram : > On 06/08/2015 01:36 PM, Baptiste Clenet wrote: > >>>> >>>> I've edited variable KERNEL_PATCHVER:=3.18 to KERNEL_PATCHVER:=4.0.4 >>>> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 installed >>> >>> >>> Also you need to specify the configuration file for 4.0.4 kernel. >>> >>> just copy the file target/linux/ramips/mt7628/config-3.18 as >>> target/linux/ramips/mt7628/config-4.0 >>> >>> I hope it will resolve this error. >>> >>> -- >>> Varka Bhadram >>> >> >> Thanks Varka, I copied the files, I'm trying to make now. On question >> came up, what about patches? There are many patches for Linux 3.18, is >> there any for Linux 4.0? target/linux/ramips/mt7628 only contains a >> folder for 3.18 patches. > > > There may be so-many patches merged into 4.0 from patches-3.18 directory..? > > I just created a directory with the name patches-4.0 under > target/linux/ramips/ . > > I think its a bad solution. But the build was successful and able generate > the > binaries in bin/ramips directory. I don't know whether these binaries > working > or not. I don't have hardware to test these binaries. > > I only copied one patch from patches-3.18 to 4.0 to fix one build error. > i.e., 0103-MIPS-OWRTDTB.patch > > Hope it helps. Its just a shoot in the dark for your problem. > > Test it and update the results. > > Thanks > > -- > Varka Bhadram > Without adding the patch 0103-MIPS-OWRTDTB.patch, I got an error: WARNING: kmod-6lowpan-iphc is not available in the kernel config - generating empty package ... ERROR: module '/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/net/bluetooth/rfcomm/rfcomm.ko' is missing. This is about a package I added in menuconfig but I need them. Those package worked well while compiling with Linux 3.18. Any idea? Varka, which configuration did you use? Only the minimal? (I mean set Target and Subtarget in menuconfig) Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-08 9:29 GMT+02:00 Varka Bhadram : > On 06/08/2015 12:54 PM, Baptiste Clenet wrote: >> >> 2015-06-07 19:24 GMT+02:00 Baptiste Clenet : >>> >>> Le 6 juin 2015 15:40, "Roman Yeryomin" a écrit : >>>> >>>> On 6 June 2015 at 09:21, Dirk Neukirchen wrote: >>>>> >>>>> On 05.06.2015 16:00, Baptiste Clenet wrote: >>>>>> >>>>>> Hi OpenWRT developers, >>>>>> >>>>>> Is there any plan to port OPENWRT on Linux 4.x? (Or is it already >>>>>> done?) >>>>>> >>>>>> >>>>> >>>>> - ar71xx: ar8216/ar8316/ar8xxx driver is broken >>>>> on 8337N and some unknown router (reported yesterday on IRC) >>>>> look at [3] if anybody is interested >>>> >>>> That was me, probably. I'm trying 4.0.4 on several ar71xx routers/APs, >>>> mostly Ubiquiti. All have the same problem: >>>> http://p.tet.rtu.lv/pbzn5sspm/wvtsep/raw >>>> I think the problem is inside ag71xx (ethernet driver) and related to >>>> timers and/or interrupts but not sure. >>>> >>>> Regards, >>>> Roman >>>> ___ >>>> openwrt-devel mailing list >>>> openwrt-devel@lists.openwrt.org >>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> >>> Hi, >>> Thanks for your answer, I'm using the board Ralink MT7628. I've just seen >>> that MT7628 board has Linux 3.18 as default. May I change to Linux 4.0.4 >>> ? >>> Will it work ? I'm going to try tomorrow. >>> >>> Cheers, >>> >>> Baptiste >> >> >> I've edited variable KERNEL_PATCHVER:=3.18 to KERNEL_PATCHVER:=4.0.4 >> in target/Linux/ramips/Makefile in order to get Linux 4.0.4 installed > > > Also you need to specify the configuration file for 4.0.4 kernel. > > just copy the file target/linux/ramips/mt7628/config-3.18 as > target/linux/ramips/mt7628/config-4.0 > > I hope it will resolve this error. > > -- > Varka Bhadram > Thanks Varka, I copied the files, I'm trying to make now. On question came up, what about patches? There are many patches for Linux 3.18, is there any for Linux 4.0? target/linux/ramips/mt7628 only contains a folder for 3.18 patches. Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
2015-06-07 19:24 GMT+02:00 Baptiste Clenet : > > Le 6 juin 2015 15:40, "Roman Yeryomin" a écrit : >> > >> On 6 June 2015 at 09:21, Dirk Neukirchen wrote: >> > On 05.06.2015 16:00, Baptiste Clenet wrote: >> >> Hi OpenWRT developers, >> >> >> >> Is there any plan to port OPENWRT on Linux 4.x? (Or is it already >> >> done?) >> >> >> >> >> > >> > >> > - ar71xx: ar8216/ar8316/ar8xxx driver is broken >> > on 8337N and some unknown router (reported yesterday on IRC) >> > look at [3] if anybody is interested >> >> That was me, probably. I'm trying 4.0.4 on several ar71xx routers/APs, >> mostly Ubiquiti. All have the same problem: >> http://p.tet.rtu.lv/pbzn5sspm/wvtsep/raw >> I think the problem is inside ag71xx (ethernet driver) and related to >> timers and/or interrupts but not sure. >> >> Regards, >> Roman >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > Hi, > Thanks for your answer, I'm using the board Ralink MT7628. I've just seen > that MT7628 board has Linux 3.18 as default. May I change to Linux 4.0.4 ? > Will it work ? I'm going to try tomorrow. > > Cheers, > > Baptiste I've edited variable KERNEL_PATCHVER:=3.18 to KERNEL_PATCHVER:=4.0.4 in target/Linux/ramips/Makefile in order to get Linux 4.0.4 installed and I got an error: touch /trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/.quilt_used touch /trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/.prepared if [ -s "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/patches/series" ]; then (cd "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4"; if quilt --quiltrc=- next >/dev/null 2>&1; then quilt --quiltrc=- push -a; else quilt --quiltrc=- top >/dev/null 2>&1; fi ); fi touch "/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/.quilt_checked" /trunk/scripts/kconfig.pl > /trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/.config.target Parse error at 3/trunk/scripts/kconfig.pl line 137. make[4]: *** [/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7628/linux-4.0.4/.configured] Error 255 make[4]: Leaving directory `/trunk/target/linux/ramips' make[3]: *** [compile] Error 2 make[3]: Leaving directory `/trunk/target/linux' make[2]: *** [target/linux/compile] Error 2 make[2]: Leaving directory `/trunk' make[1]: *** [/trunk/staging_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/stamp/.target_compile] Error 2 make[1]: Leaving directory `/trunk' make: *** [world] Erreur 2 Cheers, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Linux 4.x
Le 6 juin 2015 15:40, "Roman Yeryomin" a écrit : > > On 6 June 2015 at 09:21, Dirk Neukirchen wrote: > > On 05.06.2015 16:00, Baptiste Clenet wrote: > >> Hi OpenWRT developers, > >> > >> Is there any plan to port OPENWRT on Linux 4.x? (Or is it already done?) > >> > >> > > > > > > - ar71xx: ar8216/ar8316/ar8xxx driver is broken > > on 8337N and some unknown router (reported yesterday on IRC) > > look at [3] if anybody is interested > > That was me, probably. I'm trying 4.0.4 on several ar71xx routers/APs, > mostly Ubiquiti. All have the same problem: > http://p.tet.rtu.lv/pbzn5sspm/wvtsep/raw > I think the problem is inside ag71xx (ethernet driver) and related to > timers and/or interrupts but not sure. > > Regards, > Roman > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Hi, Thanks for your answer, I'm using the board Ralink MT7628. I've just seen that MT7628 board has Linux 3.18 as default. May I change to Linux 4.0.4 ? Will it work ? I'm going to try tomorrow. Cheers, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Linux 4.x
Hi OpenWRT developers, Is there any plan to port OPENWRT on Linux 4.x? (Or is it already done?) Wpan-tools works mainly on bluetooth-next kernel which is base on Linux 4.x so it doesn't currently work with OpenWRT. Cheers, Baptiste ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
