When using the build system, how do we make sure to use the latest versions of the MT drivers found at
https://github.com/openwrt/mt76 ? Does this have to be in our feeds.conf.default somehow?
I see recent commits in the
https://github.com/openwrt/mt76 site, but then when I do a git pull I do not see these modified files downloaded? What am I doing wrong?
Change the PKG_SOURCE_VERSION in package/kernel/mt76/Makefile to the commit hash you want.
So if I look at the top of this make file I see the following code
PKG_MAINTAINER:=Felix Fietkau <firstname.lastname@example.org>
It looks like the latests commit to this MT76 was 3 days ago
So do I just replace PKG_SOURCE_VERSION:=a94e43f277e22ce24237320ce92b1f185eff0b1
I notice the current on in the file has an "a" infront of the 94 numbers, but the latest commit doesn't. Do I put an a infront?
Here it is explained in detail.
PKG_HASH is SHA256 checksum used when you download the package as.tar.xz / .tar.gz as a pre-built archive file from upstream
PKG_MIRROR_HASH is also SHA256 and is used when you download the source with git protocol based on commit hash. As buildbot places the download sources to the server as .tar.xz, the next build can use the PKG_MIRROR_HASH to verify the package without calling upstream git server, and can re-use the source file instead of re-downloading it with git. (In practice you first o…
I am still struggling with this. How do I verify that these files have been changed / its getting the latest once I change the PKG_SOURCE_VERSION:=9406eb1d110f96e78cf376c4ed9d5164af4075e1
Do I need to change anything on the PKG_MIRROR_HASH? I don't know where to find the PKG_MIRROR_HASH
After I edit and save this, do I just do a git pull to see the changes? Or a ./scripts/feeds update -a
If anyone could include step by step on what I can do to change this that would be awesome.
I am following up here. I still was not able to get this to work. I know where to find the date, but how do you get the correct PKG_SOURCE_VERSION and PKG_MIRROR_HASH? I can't find a PKG_MIRROR_HASH when I browse github?
PKG_SOURCE_VERSION is the git commit hash. PKG_MIRROR_HASH should be generated automatically by the build system when you build. (and you'll see what it should be when it compares it to what it has and fails)
Or. you can just add:
and avoid the hash mismatch the first time out..
I download the repo:
upload that to:
copy/paste the SHA-256 hash to the make file
The issue with doing it that way, is that you are not compiling from source.
@colton.conor is trying to do compile based on a specific checkout commit, which is where
PKG_MIRROR_HASH comes from.
Also, if you are running Linux, you can just do a
sha256sum on the file to get the hash, without uploading it anywhere, but again, for the OP, it won't work..
I am trying to use the latest MT76 changes with a MT7615DN card on my router. The wireless card doesn't work wirth an error message
[ 12.644221] mt7615_common: Unknown symbol mt76_testmode_cmd (err -2)
[ 12.656971] mt7615_common: Unknown symbol mt76_testmode_dump (err -2)
[ 12.706201] PPP generic driver version 2.4.2
[ 12.716335] NET: Registered protocol family 24
[ 12.737905] mt7615_common: Unknown symbol mt76_testmode_cmd (err -2)
[ 12.750663] mt7615_common: Unknown symbol mt76_testmode_dump (err -2)
[ 12.769444] random: crng init done
[ 12.783654] kmodloader: 2 modules could not be probed
[ 12.793875] kmodloader: - mt7615-common - 0
[ 12.802282] kmodloader: dependency not loaded mt7615-common
[ 12.813456] kmodloader: - mt7615e - 1
I noticed that when the guys update their changes to openwrt source code they modify the Makefile in openwrt/package/kernel/mt76
Does anyone know what needs to be added in there?
You're better off just pulling the changes from nbd's git tree - see
You can pull those patches and apply them to your local tree.
@Borromini. Excuse my ignorance but would you have a link somewhere on how to do that?
Unfortunately I am more proficient in copy/paste tasks especially when it comes to building from source.
EDIT: I think I figured out a way to do it. Thanks for the tip
You are compiling from source right? Once you pulled in nbd's tree you can pull the patches from them like this:
$ git format-patch -1 187e5d5ff8dcdaef152b8d0fd3161fa5d5b58358
Then, in your master tree:
$ git am -i /path/to/patch
Actually thanks for posting this as it wasn't what I was doing. And yes I am building from source.