Re: [OpenWrt-Devel] Fixes for D-Link DVA-G3810BN/TL
On Wed, 2012-04-11 at 21:00 +0200, jbem...@zonnet.nl wrote: > Hi Salander, > > Yes, I studied that, but my problem is that my changes to > board_bcm63xx.c are under build_dir. I'm not sure where the original > file lives in SVN, it could be in some tar ball? > > There's several similar patches (e.g. > https://dev.openwrt.org/browser/trunk/target/linux/brcm63xx/patches-3.3/512-board_BTV2110.patch), > but I don't see against which directory those were > made? You need to use the quilt patch management tool. It's covered here http://wiki.openwrt.org/doc/devel/patches. In particular you are looking at a kernel patch. The patch you mention above is to be applied to the linux brcm63xx 3.3 kernel tree under build_dir. The birds-eye-view is that these patches are applied in the build_dir tree. With the help of quilt you will make an edit in the build_dir tree and it will become a patch in the target tree. Conor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fixes for D-Link DVA-G3810BN/TL
Hiya, If you're certain the files are part of buildroot, then someone else will need to chime in with how to handle that. To help clarify, maybe reply with the full paths of 1) where you extracted buildroot, 2) where you have your trunk working folder, 3) paths of the files you want to patch. Sent from my iPhone On 11 Apr 2012, at 20:00, jbem...@zonnet.nl wrote: > Hi Salander, > > Yes, I studied that, but my problem is that my changes to board_bcm63xx.c are > under build_dir. I'm not sure where the original file lives in SVN, it could > be in some tar ball? > > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fixes for D-Link DVA-G3810BN/TL
Hi Salander,
Yes, I studied that, but my problem is that my changes to
board_bcm63xx.c are under build_dir. I'm not sure where the original
file lives in SVN, it could be in some tar ball?
There's several similar patches (e.g.
https://dev.openwrt.org/browser/trunk/target/linux/brcm63xx/patches-3.3/512-board_BTV2110.patch), but I don't see against which directory those were
made?
Thanks,
Jeroen
Citeren Salander :
Hi Jeroen, check out this link. Should cover everything but sing out
if still unclear.
https://dev.openwrt.org/wiki/SubmittingPatches
Sent from my iPhone
On 11 Apr 2012, at 17:30, Jeroen van Bemmel wrote:
Hello,
Here´s some fixes for a D-Link DVA-G3810BN target. The first is an
edit and the second should be a patch, but I´m not sure how to make
the patch - it´s a heavily patched file
Edit:
trunk/target/linux/brcm63xx/image/Makefile
# D-Link DVA-G3810BN/TL
$(call Image/Build/CFEFIXUP,$(1),96358VW,DVAG3810BN,6358,DVAG3810BN)
Add:
linux-brcm63xx/linux-3.0.18/arch/mips/bcm63xx/boards/board_bcm63xx.c
/* D-Link DVA-G3810BN/TL */
static struct board_info __initdata board_DVAG3810BN = {
.name= "DVAG3810BN",
.expected_cpu_id= 0x6358,
.has_uart0= 1,
.has_enet0= 1,
.has_enet1= 1,
.has_pci= 1,
.enet0 = {
.has_phy= 0,// makes warnings go away
.use_internal_phy= 1,
.force_speed_100= 1,
.force_duplex_full= 1,
},
.enet1 = {
.force_speed_100= 1,
.force_duplex_full= 1,
},
.has_ohci0 = 1,
.has_pccard = 1,
.has_ehci0 = 1,
.leds = {
{
.name= "VoIP",
.gpio= 1,
},
{
.name= "DSL",
.gpio= 22,
.active_low= 1,
},
{
.name= "Internet",
.gpio= 23,
.active_low= 1,
},
{
.name= "power",
.gpio= 4,
.default_trigger = "default-on",
},
{
.name= "stop",
.gpio= 5,
},
},
.buttons = {
{
.desc= "reset",
.gpio= 10,// Not sure, 1..9, 30,31,32,33,34=wrong
.active_low= 1,
.type= EV_KEY,
.code= KEY_RESTART,
.threshold= 3,
},
},
};
[]
&board_DVAG3810BN,
Could someone put this in trunk, or explain what to do to get it added?
Thanks,
Jeroen
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fixes for D-Link DVA-G3810BN/TL
Hi Jeroen, check out this link. Should cover everything but sing out if still
unclear.
https://dev.openwrt.org/wiki/SubmittingPatches
Sent from my iPhone
On 11 Apr 2012, at 17:30, Jeroen van Bemmel wrote:
> Hello,
>
> Here´s some fixes for a D-Link DVA-G3810BN target. The first is an edit and
> the second should be a patch, but I´m not sure how to make the patch - it´s a
> heavily patched file
>
> Edit:
> trunk/target/linux/brcm63xx/image/Makefile
> # D-Link DVA-G3810BN/TL
> $(call Image/Build/CFEFIXUP,$(1),96358VW,DVAG3810BN,6358,DVAG3810BN)
>
> Add:
> linux-brcm63xx/linux-3.0.18/arch/mips/bcm63xx/boards/board_bcm63xx.c
>
> /* D-Link DVA-G3810BN/TL */
> static struct board_info __initdata board_DVAG3810BN = {
>.name= "DVAG3810BN",
>.expected_cpu_id= 0x6358,
>
>.has_uart0= 1,
>.has_enet0= 1,
>.has_enet1= 1,
>.has_pci= 1,
>
>.enet0 = {
>.has_phy= 0,// makes warnings go away
>.use_internal_phy= 1,
>.force_speed_100= 1,
>.force_duplex_full= 1,
>},
>
>.enet1 = {
>.force_speed_100= 1,
>.force_duplex_full= 1,
>},
>
>
>.has_ohci0 = 1,
>.has_pccard = 1,
>.has_ehci0 = 1,
>
>.leds = {
>{
>.name= "VoIP",
>.gpio= 1,
>},
>{
>.name= "DSL",
>.gpio= 22,
>.active_low= 1,
>},
>{
>.name= "Internet",
>.gpio= 23,
>.active_low= 1,
>},
>{
>.name= "power",
>.gpio= 4,
>.default_trigger = "default-on",
>},
>{
>.name= "stop",
>.gpio= 5,
>},
>},
>
>.buttons = {
>{
>.desc= "reset",
>.gpio= 10,// Not sure, 1..9, 30,31,32,33,34=wrong
>.active_low= 1,
>.type= EV_KEY,
>.code= KEY_RESTART,
>.threshold= 3,
>},
>},
> };
>
> []
>
> &board_DVAG3810BN,
>
> Could someone put this in trunk, or explain what to do to get it added?
>
> Thanks,
> Jeroen
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fixes for D-Link DVA-G3810BN/TL
Hello,
Here´s some fixes for a D-Link DVA-G3810BN target. The first is an edit
and the second should be a patch, but I´m not sure how to make the patch
- it´s a heavily patched file
Edit:
trunk/target/linux/brcm63xx/image/Makefile
# D-Link DVA-G3810BN/TL
$(call Image/Build/CFEFIXUP,$(1),96358VW,DVAG3810BN,6358,DVAG3810BN)
Add:
linux-brcm63xx/linux-3.0.18/arch/mips/bcm63xx/boards/board_bcm63xx.c
/* D-Link DVA-G3810BN/TL */
static struct board_info __initdata board_DVAG3810BN = {
.name= "DVAG3810BN",
.expected_cpu_id= 0x6358,
.has_uart0= 1,
.has_enet0= 1,
.has_enet1= 1,
.has_pci= 1,
.enet0 = {
.has_phy= 0,// makes warnings go away
.use_internal_phy= 1,
.force_speed_100= 1,
.force_duplex_full= 1,
},
.enet1 = {
.force_speed_100= 1,
.force_duplex_full= 1,
},
.has_ohci0 = 1,
.has_pccard = 1,
.has_ehci0 = 1,
.leds = {
{
.name= "VoIP",
.gpio= 1,
},
{
.name= "DSL",
.gpio= 22,
.active_low= 1,
},
{
.name= "Internet",
.gpio= 23,
.active_low= 1,
},
{
.name= "power",
.gpio= 4,
.default_trigger = "default-on",
},
{
.name= "stop",
.gpio= 5,
},
},
.buttons = {
{
.desc= "reset",
.gpio= 10,// Not sure, 1..9, 30,31,32,33,34=wrong
.active_low= 1,
.type= EV_KEY,
.code= KEY_RESTART,
.threshold= 3,
},
},
};
[]
&board_DVAG3810BN,
Could someone put this in trunk, or explain what to do to get it added?
Thanks,
Jeroen
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
