Hi,
I'm currently working on bringing OpenWRT support to the RouterBOARD RBM33G [1].
The device is based on the mt7621 SoC and has two spi nor-flash chips.
The first chip is very small (512 kB) and connected to CS0. The second
chip is a lot larger (16 MB) and connected to CS1.
The mt7621-spi
On Sat, Apr 28, 2018 at 9:55 PM, Daniel Golle wrote:
> Some options' default values have been changed upstream, others were
> accidentally inverted (CONFIG_WOLFSSL_HAS_DES3). Also add options
> needed to build hostapd/wpa_supplicant against wolfssl.
Sorry for the late
Hi Alex,
On Thu, 3 May 2018, Alex Guo wrote:
Hi,
I'm Alex from Jinglue Semi. Shanghai.
I did some work on porting OpenWrt to RISC-V. Right now it based on
OpenWrt master branch and use upstream toochain (gcc/7.3.0, Binutils
2.30 and glibc 2.27). I am still working on use vanilla kernel
Hi
On Wed, 2 May 2018, Linus Walleij wrote:
> On Sun, Apr 29, 2018 at 8:32 PM, Roman Yeryomin wrote:
>
> > I've prepared 4.14 branch here
> > https://github.com/yeryomin/openwrt/commits/gemini-4.14
> > I think it can be merged in it's current state. The only problem I'm aware
>
On Wed, May 2, 2018 at 10:01 AM, Linus Walleij wrote:
> Network does not come up either, I suspect it is because of missing the
> Realtek PHY driver, so will investigate this further.
I found the culprit, sent you a patch adding ethernet to the
DNS-313 and Wiliboard
This adds an interrim patch for v4.14 based on an
upstream commit to get ethernet working on D-Link DNS-313
(probably also on the Wiliboards)
Signed-off-by: Linus Walleij
---
...-dts-Add-ethernet-to-a-bunch-of-platforms.patch | 123 +
1 file
Hi
On Wed, 2 May 2018, Joel Wirāmu Pauling wrote:
> It's Cortina but arm7 IIRC; there was a NDA available SDK for it based on
> 2.6.something - which I started to go through the process of getting access
> too a few years ago, but the platform was bought out by Realtek who
> scuttled it as it
Hi,
I'm Alex from Jinglue Semi. Shanghai.
I did some work on porting OpenWrt to RISC-V. Right now it based on
OpenWrt master branch and use upstream toochain (gcc/7.3.0, Binutils
2.30 and glibc 2.27). I am still working on use vanilla kernel but there
are some build issues to fix.
You can
sorry this is my first time i'll follow the rules now!
Il 02/05/2018 16:09, Alberto Bursi ha scritto:
Next time please update the PR, don't close and open a new one. See
the paragraph about squashing commits in the submitting patches page
in the wiki for how to do it with git
On 2018-05-02 11:01, Linus Walleij wrote:
On Wed, May 2, 2018 at 12:18 AM, Linus Walleij
wrote:
On Sun, Apr 29, 2018 at 8:32 PM, Roman Yeryomin
wrote:
Linus, could you test that branch on your device and see if network
is
working by default?
It's Cortina but arm7 IIRC; there was a NDA available SDK for it based on
2.6.something - which I started to go through the process of getting access
too a few years ago, but the platform was bought out by Realtek who
scuttled it as it was in competition with their own designs.
The Almond+ has
On Wed, May 2, 2018 at 12:41 AM, Joel Wirāmu Pauling wrote:
> any chance for support for the
> Goldengate SoC found in the Almond+. Currently attempting to reuse it for a
> home automation project but it's ancient kernel is terrible and even doing
> basic things like vlans are
On Wed, May 2, 2018 at 12:18 AM, Linus Walleij wrote:
> On Sun, Apr 29, 2018 at 8:32 PM, Roman Yeryomin wrote:
>>
>> Linus, could you test that branch on your device and see if network is
>> working by default?
>
> I've pulled in the branch and building
Since the D-Link devices boot from hard disk we need to
add the following changes to Gemini:
- Supply a bootarg in the device tree so we can boot from
the right partition (/dev/sda4 on DNS-313)
- Disable forced command line in config so the kernel picks
up the right bootargs from the device
14 matches
Mail list logo