ter, I could have
donated like 2x of its price towards the goal of its software
liberation (if there would be any crowdfunding). Also, being able to
run on 100% opensource will surely attract a lot of FSF-minded buyers
On Thu, Apr 11, 2024 at 1:20 PM Daniel Golle wrote:
>
> Hi Ivan,
>
> On
", stored in silicon
BootROM is considered by Free Software Foundation as a part of
hardware, + it is not as bad as those bloated&buggy binary blobs
running at your OpenWRT space
On Thu, Apr 11, 2024 at 9:51 AM Piotr Dymacz wrote:
>
> Hi,
>
> On 11.04.2024 10:52, Bjørn Mork wrote:
&
> SOC: MediaTek MT7981B , Wi-Fi: MediaTek MT7976C
Are these Mediateks capable of working without any binary blobs, at
least in theory? (i.e. some existent reverse-engineering research)
If not, why have they been chosen in particular? IMHO the "OpenWRT
One" project hardware should not be worse than
> My 2 cent on the problem of permitting nick is that if we accept that,
> some funny guy might use nickname like "ExtraHardCockSucker"
> and we wouldn't have anything to say about it and have to accept
> it if the contribution is correct.
An immature person who uses such a nickname - is quite unl
WiFi chip
by crowdfunding). There are no other sane options in sight
> Dave Taht wrote:
> I would actually, be happy cutting even more multiplexing latency out of the
> ath9k chips
Best regards,
Ivan
On Tue, Feb 27, 2024 at 9:21 AM Bas Mevissen via openwrt-devel
wrote:
>
> The s
te a new WiFi chip
by crowdfunding). There are no other sane options in sight
> Dave Taht wrote:
> I would actually, be happy cutting even more multiplexing latency out of the
> ath9k chips
Best regards,
Ivan
___
openwrt-devel mailing
JFY, this series of commits broke Gl.Inet mt-1300 beryl(mt7621) - I've
had to revert it in my local build. So basically the problem is that
device cannot read it's mac from partition and every reboot it
generates a new one.
пн, 19 июл. 2021 г. в 17:32, Ansuel Smith :
>
> hi,
> some dtsi still use
0-0x000e : "u-boot-env"
[3.660548] 0x000e-0x0014 : "factory"
[3.671742] 0x0014-0x0044 : "kernel1"
[3.683089] 0x0044-0x0074 : "kernel2"
[3.694255] 0
Piotr,
> On 11 Nov 2019, at 21:35, Piotr Dymacz wrote:
>
> Hi Ivan,
>
> On 11.11.2019 19:09, Ivan Baktsheev wrote:
>> Hi,
>> I want to add new device, but as of now I can upload firmware wirelessly and
>> then I need to connect using wired connection, b
Hi,
I want to add new device, but as of now I can upload firmware wirelessly and
then I need to connect using wired connection, because in stock OpenWrt image
wireless is disabled.
For my router (and probably many others) default WiFi SSID stored in factory
partition and it’s quite easy to ext
983>
Thanks, Ivan
> Am 20.09.2019 um 15:10 schrieb Ivan Hörler :
>
> I tried to compile the package libmraa as single and have some problems with
> the dependencies:
>
> Followed this: https://openwrt.org/docs/guide-developer/single.package
> <https://op
/compile' failed
make: *** [package/libgcc1/compile] Error 2
Why do i not find the dependency libgcc1 in 'make menuconfig' search (/)?
Thanks, Ivan
> Am 19.09.2019 um 20:18 schrieb Ivan Hörler :
>
> Hi
> I have problems makeing libmraa working on Linkit Smart 7688.
nges in error output.
what am i missing?
Thanks for comments, Ivan Hörler___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> Am 15.09.2019 um 22:46 schrieb Daniel Golle :
>
> Hi Ivan,
>
> On Sun, Sep 15, 2019 at 09:28:35PM +0200, Ivan Hörler wrote:
>> Hi
>> Now after nowing how to make a PR, im interested to know how you think about
>> some thaughts of me.
>>
>> Link
. mraa from Intel
6. some upm modules from Intel
What of this list wold be possible to integrate in to a official openWRT
release without scratching rules?
Regards, Ivan Hörler
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https
again from not DMARC rejected google account. see below. thanks
> Am 15.09.2019 um 12:57 schrieb Ivan Hörler via openwrt-devel
> :
>
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" head
did: https://github.com/openwrt/openwrt/pull/2411
Thanks for the help!
Ivan
> Am 14.09.2019 um 22:18 schrieb Adrian Schmutzler :
>
> Hi, thanks for implementing my suggestions. However, please do not open a new
> PR when doing changes, but rebase your commits in the existing branch in the
&
Hi Adrian
Thanks for your patientness. Wasn’t aware it's so strict. I just added the
--signedoff to the commit.
Good to know how to work clean. Now i redone it.
Is this fullfilling openWRT’s rules?
https://github.com/openwrt/openwrt/pull/2411
Regards, Ivan
> Am 14.09.2019 um 16:27
Hi
so i did: https://github.com/openwrt/openwrt/pull/2410
Thanks for comments if its done wright or not. It’s my first.
Regards, Ivan Hörler
> Am 13.09.2019 um 22:41 schrieb Adrian Schmutzler :
>
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [m
Hi
I have a question about how openwrt handles packages needed by a target.
The Linkit Smart 7688 has a SD-Card reader that does not work with the official
build of openwrt 18.06.
Adding kmod-sdhci-mt7620 makes it working.
I think it would be nice to get a fully working device when updateing wit
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi
I have a question about how ope
On 2018-12-21 at 05:07 +0300, Ivan Shapovalov wrote:
> Hey,
>
> (I'm sorry if I'm writing to a wrong list but I don't see any other
> channels apart from #openwrt which is likely not watched by anyone.)
>
> I have a multi-uplink setup on a mt7621-based router (X
uplinks are correctly
handled, but requests on port 80 are only responded on "rtk" uplink and
time-out on "onl" uplink.
Observations:
If I change the catch-all routing rule (priority 40002) to point to
"onl" table, the situation reverses.
If I kill the Ngin
On Sat, 15 Dec 2018 22:49:20 +0100
Petr Štetiar wrote:
> > Its a bit strange situation: OpenWRT contain few dozen rt3xxx dts
> > profiles, and you will build all of them, ecxept few new added. I
> > dont know how often image generetad for all boards, but at least
> > once per month or for releas
On Sat, 15 Dec 2018 14:08:39 +0100
Jo-Philipp Wich wrote:
> I'd favor accepting the basic board support for such boards but
> disabling the image generation (commented out).
Its a bit strange situation: OpenWRT contain few dozen rt3xxx dts profiles, and
you will build all of them, ecxept few ne
> I would like to start to reject patches for adding boards with only
> 32 MByte of RAM and 4 MByte of flash [0]. These boards barely work
> with todays OpenWrt default builds and require quite some
> modifications to be useful at all [1].
>
> IMHO it doesn't make much sense to waste resources (
This patch adds support for Omnima MiniCloudless MT7620 + MT76x12
Concurrent Dual Band platform.
Tested on the board and patch applies to OpenWrt r49119 checked out on
7th April 2016.
Signed-off-by: Ivan Ignjatic
---
diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds
b
y
CONFIG_PACKAGE_librt=y
CONFIG_PACKAGE_objdump=y
CONFIG_PACKAGE_screen=y
CONFIG_PACKAGE_strace=y
CONFIG_PACKAGE_throw-catch-sigsegv=y
CONFIG_PACKAGE_uclibcxx=y
CONFIG_TARGET_EXT4_BLOCKSIZE=4096
CONFIG_TARGET_EXT4_BLOCKSIZE_4K=y
CONFIG_TARGET_EXT4_MAXINODE=6000
CONFIG_TARGET_EXT4_RESERVED_PCT=0
CONFIG_TARGET_ROOT
This patch adds support for the Omnima MiniPlug RT5350 based board, 8MB SPI
flash
Signed-off-by: Ivan Ignjatic
---
Index: target/linux/ramips/base-files/etc/uci-defaults/01_leds
===
--- target/linux/ramips/base-files/etc/uci
with this patch.
Signed-off-by: Ivan Ignjatichttp://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel>>
---
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig
===
--- target/linux/ramips/files/arch/mips/
30 matches
Mail list logo
