source code scans. So I asked if that kind of support built in to
> openwrt build system would be a nice to have feature.
>
>
>
>
>
> Karthik Bollam
>
>
>
>
> *From: *James Hilliard
> *Sent: *Wednesday, October 14, 2015 11:54 AM
> *To: *Samba Siva Karthik
I think you can just use a custom package feed. That's how I've done
it(although I don't use it for proprietary code so much as out of tree
packages).
On Wed, Oct 14, 2015 at 1:50 PM, Samba Siva Karthik Bollam <
sambabol...@hotmail.com> wrote:
> Hi
>
>I worked with Qualcomm and Intel on their
What do you think about using something like Jira for project
management(which is free for open source projects)? I know it was used by
cyanogenmod with decent success. One other potential advantage would be the
possibility of CI testing being tied in more closely.
On Mon, Oct 12, 2015 at 1:46 AM,
I'm looking to manage cgminer's json formatted config files using uci, the
part I'm confused about is how to handle edits to the config that are done
by the application(cgminer) itself. Could uci be extended to handle json
formatted configs directly? Using intermediary uci configs could cause sync
all as possible as well. I created the patch using a git diff and it
seemed to apply when I used git apply, did my mail client mess up the
formatting?
On Sun, May 10, 2015 at 5:23 AM, Felix Fietkau wrote:
> On 2015-05-02 05:08, James Hilliard wrote:
>> I did my best to separate this
aw,ARCHERC7V2,archer-c7-v2,ARCHER-C7,ttyS0,115200,0xc702,1,16Mlzma))
+$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,ANTMINER,bitmain-antminer,TL-WR741ND-v4,ttyATH0,115200,0x07430002,1,8Mlzma))
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,ELM150,el-m150,EL-M150,ttyATH0,115200,0x0150010
The Antminer S1 and S3 use a controller with a modified version of
OpenWRT which has a single ethernet port and a wifi antenna header.
This is the patch from their GPL source release which appears to break
support for the tl-wr741nd-v4 in order to support their board. What
would be the proper way t
t stand out
as needing to be configured in openwrt for this NAND chip to function
correctly?
On Wed, Mar 4, 2015 at 10:00 AM, Conor O'Gorman wrote:
> On 22/02/15 01:36, James Hilliard wrote:
>>
>> I've been trying to install OpenWRT on an Actiontec MI424WR Rev I,
>&g
I've been trying to install OpenWRT on an Actiontec MI424WR Rev I, however
some variants of this router use a Hynix NAND chip that OpenWRT doesn't
seem to be able to access. There are other versions of this router that use
a Eon NAND chip that works fine. I've attached the full boot-log. The stock
Seems there might be some relevant code here for the flash
https://github.com/jameshilliard/R7000-V1.0.2.164_1.0.15_GPL/tree/master/src/shared
On Mon, May 12, 2014 at 11:30 PM, Rafał Miłecki wrote:
> On 12 May 2014 21:50, Andre Valentin wrote:
> > The problems I have is that I do not know how
I also found the driver for the EN2210
https://github.com/jameshilliard/Quattro_2.1/blob/5a9f386e9ed9878a600cf6ea723ad9e329a27781/gpl/kernel/2.6.18/drivers/net/entrmoca/GPL/E1000/READMEwhich
may work with the earlier revision mi424wr routers.
On Tue, Apr 29, 2014 at 3:12 PM, James Hilliard
wrote
I came across this
https://github.com/jameshilliard/WECB-VZ-GPL/tree/adfad80b3144c788efb636d5acfcdd6ed91b3d79/rtl819x/drivers/mocadriver
which would appear to be the same one used for the mi424wr Rev I and
possibly some other revisions of the mi424wr. It seems to have a binary
firmware component as
Maybe they took some of my suggestions when I sent GPL notices to them
http://sourceforge.net/projects/officiallinksysfirmware/files/ although
they still haven't complied with a number of the requests for certain
devices.
On Wed, Jan 15, 2014 at 12:15 PM, Chirag Chhatriwala wrote:
> Hi,
>>
>> we
I had emailed them but never heard back, Ill see if I can find a better way
to contact them.
On Fri, Jan 10, 2014 at 2:38 AM, Marco Antonio Mauro wrote:
> Any news, James?
>
> On Fri, Oct 18, 2013 at 6:54 PM, James Hilliard
> wrote:
> > Ok, i'm going to contact the man
52 AM, Pavel Simerda wrote:
> - Original Message -
> > From: "James Hilliard"
> > To: "OpenWrt Development List"
> > Sent: Thursday, December 5, 2013 7:36:56 AM
> > Subject: Re: [OpenWrt-Devel] Interest in a openwrt router database to
> p
I would say that the best thing to do would be to tie a replacement TOH
directly into version control and have supported router models populate
directly from there somehow. Maybe something along the lines of how
cyanognmod uses their template system
http://wiki.cyanogenmod.org/w/Template:Device_inf
It might mappable against the driver binary or kernel image. Kind of
depends on what it is in it.
On Mon, Nov 11, 2013 at 1:39 PM, Bastian Bittorf wrote:
> * Ben West [11.11.2013 20:36]:
> > I am assuming incidents like these are occurring due to an ill-behaved
> > process (or processes) attemp
I can take a look at it and see if there is anything interesting, I might
be able to get it disassembled if its any sort of executable. It might just
be an array or something though.
On Mon, Nov 11, 2013 at 12:56 PM, Ben West wrote:
> Hmm, actually I discovered that wpa_supplicant apparently wr
Well, I decided to try and package device specific broadcom drivers
together for ARM. I got to the point of them compiling alongside the kernel
and creating the kernel_menuconfig section for them, but I don't really
understand the OpenWRT packaging system well enough to get them fully
integrated in
h as objcopy via a symbol rename (i.e. memcpy to
osl_memcpy).
*/
On Sun, Nov 3, 2013 at 2:25 AM, James Hilliard wrote:
> That patch included a bit more than just the modifications needed to
> support the wl driver, that patch should be for the new broadcom ARM
> architecture. I think m
u wrote:
> On 2013-11-02 23:47, James Hilliard wrote:
> > I'm not actually trying to use a fully compiled .ko file, the file is a
> > .o file such as wl_apsta.o(tools indicate it is a relocatable ELF for
> > ARM) that gets compiled into a .ko when you build GPL tarballs.
wrote:
> On 2013-11-02 08:59, James Hilliard wrote:
> > Well, maybe they didn't create the shared code because of the GPL but
> > they can't link a binary directly to a GPL component, only a LGPL
> > component I think or something like that. I've object dumped a
nternally? All the decompilers I used indicated the
drivers were relocatable ELF's and I didn't see any external memory
addresses referenced from any functions.
On Sat, Nov 2, 2013 at 2:05 AM, Felix Fietkau wrote:
> On 2013-11-02 00:30, James Hilliard wrote:
> > It's a ve
s.
> Thank you for the write up.
> I'm sorry I don't have any technical to contribute here, I'm fairly noob
> when it comes to patching drivers/kernels.
>
> Chirag
>
>
> On Fri, Nov 1, 2013 at 3:21 PM, James Hilliard
> wrote:
>
>> From what I c
n 11/01/2013 01:22 PM, James Hilliard wrote:
> > I noticed that there is a broadcom ARM build option but it only seems to
> > build for the r6250 and I'm not sure if its actually making installable
> > builds. I have a number of very large patches that are part of the build
&
I noticed that there is a broadcom ARM build option but it only seems to
build for the r6250 and I'm not sure if its actually making installable
builds. I have a number of very large patches that are part of the build
system for these routers. Has anyone been working on these recently? The
broadcom
Yeah, both should be ubicom based. Are there any left in the fire sale?
On Oct 23, 2013 9:19 AM, "valent.turko...@gmail.com" <
valent.turko...@gmail.com> wrote:
> I'm not in possestion of these routers, I just got some offer for firesale
> of these devices (really cheap) so I'm in process of orde
I'll see where i'm at this weekend in the way of progress. I'll try and
compile a stock build with dropbear so that its possible to at least start
poking around. Can you try and get a serial log from this router? Might be
helpful to see the actual boot process if possible. Also see if you can get
t
ent.
>
> Ultra performs the board initialization and then spawns U-Boot on another
> thread, and continues to run in parallel with Linux. The U-Boot console
> should be enabled but it expects to talk to a programming dongle and not an
> actual serial port.
>
>
>
> James H
27;t be too big an issue. Ill look into this more tomorrow and
start integrating the patches from the internal openwrt sources.
On Sat, Oct 19, 2013 at 5:36 AM, Jonas Gorski wrote:
> On Sat, Oct 19, 2013 at 11:04 AM, James Hilliard
> wrote:
> > I've now based off of trunk
onfigure scripts actually need this and how to fix it.
It does not exist in the oem ubicom buildroot directory as far as I can
tell so I think I just need to kill off whatever is asking for the file
since it is probably not needed there.
On Fri, Oct 18, 2013 at 6:15 AM, James Hilliard
wrote:
&g
Ok, i'm going to contact the manufacturer directly then and see what they
say.
On Fri, Oct 18, 2013 at 6:17 AM, Marco Antonio Mauro wrote:
>
> On Oct 18, 2013 1:00 PM, "James Hilliard"
> wrote:
> >
> > Does the software appear to be customized at all for the
integrating the device specific patches. Should I submit a patch for
that removal?
On Thu, Oct 17, 2013 at 6:50 AM, James Hilliard
wrote:
> So, I think i more or less got the boot processes down, however I don't
> have hardware with me right now. Boot goes from ultra>uboot>lin
.technicolor.com/en/hi/minisites/open-software/dsl-cable-ip-modem-gateways/dsl-gateways
On Fri, Oct 18, 2013 at 4:03 AM, Marco Antonio Mauro wrote:
> On Fri, Oct 18, 2013 at 10:37 AM, James Hilliard
> wrote:
> > What ISP is this issued by? Do you have a link to this modem on their
What ISP is this issued by? Do you have a link to this modem on their
website?
On Fri, Oct 18, 2013 at 3:25 AM, Jacek Kikiewicz wrote:
>
> On 18.10.2013 10:22, Marco Antonio Mauro wrote:
>
>> On Fri, Oct 18, 2013 at 10:18 AM, Jacek Kikiewicz wrote:
>>
>>> Well, if boot loader is not supported
I've been working with someone with a similar one myself the ZTE ZXV10
H108L router modem from Wind Hellas, it has a u-boot bootloader and runs
linux. http://pastebin.com/EXzrEwfE is the serial log and
http://pastebin.com/H5nbgr3i is printenv, I have issued a GPL source code
request to the operator
penwrt's port which compiles but has no
> ethernet switch enabled/ported. I's hard to test develop anything without
> flash programmer so i dropped testing. It would be nice if you could add
> this model to your work
>
> Thanks,
> Michal
>
>
> Dnia 16 paździe
f you have any suggestions. I'm not sure what this is
using for include/site and that's what I'm currently hung up on.
On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli wrote:
> Hello,
>
> 2013/9/16 James Hilliard :
> > Anyone interested in OpenWRT on Ubicom? They
Wed, Sep 18, 2013 at 6:28 AM, Gert Doering wrote:
> Hi,
>
> On Wed, Sep 18, 2013 at 05:45:26AM -0500, James Hilliard wrote:
> > I thought DD-WRT was only using public tarball drivers.I looked through
> > their source and everything seems to match up with tarbar type wl.o
I thought DD-WRT was only using public tarball drivers.I looked through
their source and everything seems to match up with tarbar type wl.o files
and so on.
On Wed, Sep 18, 2013 at 5:37 AM, Felix Fietkau wrote:
> On 2013-09-18 12:31 PM, James Hilliard wrote:
> > Aren't all th
working WiFi
is much more important than that. I'm fairly sure the other projects have
managed to work around the kernel issue for the most part without being
forced to give up on using devices specific drivers.
On Wed, Sep 18, 2013 at 4:47 AM, Felix Fietkau wrote:
> On 2013-09-
he reason for many problems. I was under the impression
> that the wl_ap.o wl_apsta.o and wl_sta.o binary's were not really kernel
> specific and only wl.ko is kernel specific, is that correct?
>
>
> On Sun, Sep 15, 2013 at 11:24 AM, Hauke Mehrtens wrote:
>
>> On 09/15
Did anyone actually get it running? Or was it just the reference code? I
have what should be device ready source.
On Mon, Sep 16, 2013 at 6:11 AM, Florian Fainelli wrote:
> Hello,
>
> 2013/9/16 James Hilliard :
> > Anyone interested in OpenWRT on Ubicom? They used OpenWR
Anyone interested in OpenWRT on Ubicom? They used OpenWRT internally so
there is already source ready(may be a little outdated though). Also have
some router specific sources of both it and stock.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt
wl_ap.o wl_apsta.o and wl_sta.o binary's were not really kernel
specific and only wl.ko is kernel specific, is that correct?
On Sun, Sep 15, 2013 at 11:24 AM, Hauke Mehrtens wrote:
> On 09/15/2013 05:40 PM, James Hilliard wrote:
> > From what I'm seeing everyone is patching
45 matches
Mail list logo
