On Thu, Sep 01, 2005 at 05:39:15PM +0200, Pavel Machek wrote:
> Hi!
>
> > > The 4020 and 0402 look oddly symmetrical to me, but that could just
> > > be my imagination.
> >
> > All I saw in it was byte n+1 = byte n >> 1. Can't see any use to that
> > either, though. Maybe it's just there to torme
Hi!
> > The 4020 and 0402 look oddly symmetrical to me, but that could just
> > be my imagination.
>
> All I saw in it was byte n+1 = byte n >> 1. Can't see any use to that
> either, though. Maybe it's just there to torment reverse engineerers, or
> trap memory corruption?
I had seen something l
Hi.
On Thu, 2005-09-01 at 13:29, Kyle Moffett wrote:
> The 4020 and 0402 look oddly symmetrical to me, but that could just
> be my imagination.
All I saw in it was byte n+1 = byte n >> 1. Can't see any use to that
either, though. Maybe it's just there to torment reverse engineerers, or
trap memor
On Aug 31, 2005, at 16:32:11, Vojtech Pavlik wrote:
On Wed, Aug 31, 2005 at 08:53:19PM +0100, Russell King wrote:
On Wed, Aug 31, 2005 at 12:55:12PM -0400, Mark Lord wrote:
I'll try loading the works into another ARM
system I have here, and see (1) if it runs as-is,
and (2) what the disassemb
>Each of the first three large parts starts with this sequence of bytes
Actually, the byte structure of the first 0x100 bytes
of each section seems to be very similar.
Some kind of header.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
On Wed, Aug 31, 2005 at 08:53:19PM +0100, Russell King wrote:
> On Wed, Aug 31, 2005 at 12:55:12PM -0400, Mark Lord wrote:
> > I'll try loading the works into another ARM
> > system I have here, and see (1) if it runs as-is,
> > and (2) what the disassembly shows.
>
> You can identify ARM code qui
On Wed, Aug 31, 2005 at 12:55:12PM -0400, Mark Lord wrote:
> I'll try loading the works into another ARM
> system I have here, and see (1) if it runs as-is,
> and (2) what the disassembly shows.
You can identify ARM code quite readily - look for a large number of
32-bit words naturally aligned and
On Wed, Aug 31, 2005 at 12:55:12PM -0400, Mark Lord wrote:
> Mmm.. curious sequence in the first 512 bytes of
> the DWL-G730AP firmware binary. It has this
> sequence of bytes repeated several times:
>
> 81 40 20 10 08 04 02 81 40 20 10 08 04 02 ...
>
> That should be recognizable to somebody
Mmm.. curious sequence in the first 512 bytes of
the DWL-G730AP firmware binary. It has this
sequence of bytes repeated several times:
81 40 20 10 08 04 02 81 40 20 10 08 04 02 ...
That should be recognizable to somebody, I think.
I'll try loading the works into another ARM
system I have her
I've been looking into the airlink devices (fry's house brand) and they
have a marvell based AP (the one that made /. a few weeks go, sells for
$17 on sale). when I contacted airlink about getting the source they
replaied that current versions only run in-house developed code, no eCos
or uCLinu
On Tue, Aug 30, 2005 at 07:49:05PM +0400, Michael Tokarev wrote:
> Vojtech Pavlik wrote:
> > Hi!
> >
> > The D-Link DWL-G730AP devices from the Kernel Summit run Linux, And it's
> > likely a GPL violation, too, since sources are nowhere to be found.
> >
> > They're based on a Marvell Libertas AP-
Vojtech Pavlik wrote:
> Hi!
>
> The D-Link DWL-G730AP devices from the Kernel Summit run Linux, And it's
> likely a GPL violation, too, since sources are nowhere to be found.
>
> They're based on a Marvell Libertas AP-32 (ARM9) design, similar
> to the ASUS WL-530g. A bootlog from the ASUS (which
> > According to http://sources.redhat.com/ecos/, it is either still RedHat
> > or already transferred to the FSF. That doesn't sound like dual
> > licensing, I don't think the FSF would do that...
>
> That was my thinking, too.
eCos at least historically had other licensing options too.
-
To u
On Tue, Aug 30, 2005 at 02:56:49PM +0200, Harald Welte wrote:
> > The device's ESSID during boot is 'Marvell AP-32', and the Libertas
> > AP-32 and AP-52 design toolkits contain only ports of Linux and eCos to
> > the device, according to Marvell. Considering the device's routing
> > capabilities
On Tue, Aug 30, 2005 at 02:18:10PM +0200, Vojtech Pavlik wrote:
> > If it is from the ASUS, what makes you think that the D-Link runs the
> > same OS? It is quite often the case that one chipset design has
> > multiple operating systems ported to it (you see systems with the same
> > broadcom or
On Tue, Aug 30, 2005 at 12:19:59PM +0200, Harald Welte wrote:
> > The D-Link DWL-G730AP devices from the Kernel Summit run Linux, And it's
> > likely a GPL violation, too, since sources are nowhere to be found.
>
> *lol*. Interestingly they must have twiddled the IP stack since when I
> tried an
On Tue, Aug 30, 2005 at 10:55:22AM +0200, Vojtech Pavlik wrote:
> Hi!
>
> The D-Link DWL-G730AP devices from the Kernel Summit run Linux, And it's
> likely a GPL violation, too, since sources are nowhere to be found.
*lol*. Interestingly they must have twiddled the IP stack since when I
tried an
Hi!
The D-Link DWL-G730AP devices from the Kernel Summit run Linux, And it's
likely a GPL violation, too, since sources are nowhere to be found.
They're based on a Marvell Libertas AP-32 (ARM9) design, similar
to the ASUS WL-530g. A bootlog from the ASUS (which has telnet enabled
for some reason,
18 matches
Mail list logo
