It it used by brcm47xx and bcm53xx targets, so put patches in generic.
Signed-off-by: Rafał Miłecki
---
V2: Update bcm53xx kernel config
V3: Use V2 of patch for "nvram" partition (avoids two "nvram"s)
V4: Name patches according to the target/linux/generic/PATCHES
---
target/linux/bcm53xx/config-
Hi,
On 18.08.2014 01:43, Daniel Golle wrote:
> Hi!
>
> I was thinking about porting wayland/weston to OpenWrt for a while.
> Now I finally searched for that I saw that it has already been done!
> I love it when that happens, reaching a goal with no efforts involved :)
> Thank you Oskari for rpi-ope
On 08/18/2014 08:59 PM, Rafał Miłecki wrote:
> It it used by brcm47xx and bcm53xx targets, so put patches in generic.
>
> Signed-off-by: Rafał Miłecki
> ---
> V2: Update bcm53xx kernel config
> V3: Use V2 of patch for "nvram" partition (avoids two "nvram"s)
> ---
> .../027-mtd-bcm47xxpart-get-nv
There is a group of devices that lzma-loader doesn't work with. They
simply hang at "Starting program at 0x80001000" which is really hard to
debug and we didn't find any solution for this for years.
Broadcom doesn't use lzma-loader on these devices anyway. They decided
to drop lzma-loader and use
It it used by brcm47xx and bcm53xx targets, so put patches in generic.
Signed-off-by: Rafał Miłecki
---
V2: Update bcm53xx kernel config
V3: Use V2 of patch for "nvram" partition (avoids two "nvram"s)
---
.../027-mtd-bcm47xxpart-get-nvram.patch| 4 +-
.../390-mtd-bcm47xxpart-backpor
Hi Owen,
On 08/18/2014 10:48 AM, Owen Kirby wrote:
> It's been a while since I submitted this to the mailing list. Has anyone
> had an opportunity to take a look at this patch? Anything I can do to
> help move it forward?
I have placed it in patchwork as "Under review", will probably get it
commi
It's been a while since I submitted this to the mailing list. Has anyone
had an opportunity to take a look at this patch? Anything I can do to
help move it forward?
Thanks,
Owen
On 14-06-11 02:38 PM, Owen Kirby wrote:
The AT91 family of SoCs have a USB device controller, this patch
should ena
On Mon, 18 Aug 2014 09:10:24 -0700, Michael Richardson
wrote:
José Vázquez wrote:
>> José Vázquez wrote: > According to the info i
>> could find the cpu is a 400MHz arm1176 > (ARMv6k) with VFP and C55x
>> DSP for VoIP, that runs in big endian mode; > seems that shares some
>
José Vázquez wrote:
>> José Vázquez wrote: > According to the info i
>> could find the cpu is a 400MHz arm1176 > (ARMv6k) with VFP and C55x
>> DSP for VoIP, that runs in big endian mode; > seems that shares some
>> features with TI Davinci, OMAP2 and/or Sitara.
>>
>> Seem
2014-08-18 15:19 GMT+02:00, Michael Richardson :
>
> José Vázquez wrote:
> > According to the info i could find the cpu is a 400MHz arm1176
> > (ARMv6k) with VFP and C55x DSP for VoIP, that runs in big endian
> mode;
> > seems that shares some features with TI Davinci, OMAP2 and/or Sit
Hi,
I am trying to get ACS working on my available devices.
What I have noticed is that the command `iw phy phy0 survey dump`
returned different result between HiWiFi HC6361 which uses ath9k
driver and a MT7620A based device using rt2x00 driver. On HC6361,
the command displayed statistics for a
José Vázquez wrote:
> According to the info i could find the cpu is a 400MHz arm1176
> (ARMv6k) with VFP and C55x DSP for VoIP, that runs in big endian mode;
> seems that shares some features with TI Davinci, OMAP2 and/or Sitara.
Seems to be too slow to operate enough counters for fq
I think that could be interesting add a target for Puma5 cable SoCs
family. There are tw targets: the most common is Avalanche and the
other is Volcano (maybe only for cablemodems with one ethernet port
and without WLAN).
According to the info i could find the cpu is a 400MHz arm1176
(ARMv6k) with
13 matches
Mail list logo
