On Saturday, March 02, 2013 06:39:06 Petr Štetiar wrote:
> (here it hangs and waits for a watchdog timeout)
>
> I wonder if it's a known problem or if I'm the only one affected (I
> couldn't find anything like this in the Trac).
Looks like a regression to me because it works[tm] for me. Is this
On Wednesday, March 06, 2013 22:51:15 Paul van Gool wrote:
> what SVN branch and revision are you using? I can switch to that for now.
I am currently using trunk r35506:
$ cat /etc/openwrt_version
r35506
$ cat /proc/cpuinfo
system type : Atheros AR9341 rev 1
machine
On Thursday, March 07, 2013 07:51:00 Paul van Gool wrote:
> so I built r35506 and flashed my OM2P-HS with it. As before booting the
> device work fine (which is different than what Petr observed).
>
> [..]
>
> And I never see any SSID beacons.
>
> So do you have wifi up on your OM2P-HS?
You are
On Friday, March 08, 2013 10:28:01 Paul van Gool wrote:
> I have verified that r35506 does not have that problem. No more of that
> messages in dmesg, and I can see SSID beacons.
You are welcome. I think AA could be fixed too if you contact the mac80211
maintainer to let him know about this regre
On Saturday, March 09, 2013 01:57:30 Petr Štetiar wrote:
> > f18e3c6b67f448ec47b3a5b242789bd3d5644879
> > Author: Mohammed Shafi Shajakhan
> > Date: Mon Jun 18 13:13:30 2012 +0530
> >
> > ath9k_hw: avoid possible infinite loop in ar9003_get_pll_sqsum_dvc
>
> I've reverted this patch and it
Hi Luka,
> I've added MAINTAINERS file to the openwrt-routing git repository.
> Please update that file with your real name and valid email address,
> reply to this email that you did so and tell us your github account
> name.
>
> I'm going to remove access to those of you who don't do the above
On Monday 07 October 2013 10:08:55 Luka Perkov wrote:
> > maybe I am the only one who does not know what is going on but who are you
> > to mandate what is happening with the openwrt-routing feed ? I don't
> > remember you being present when this feed was created. Did we choose a
> > benevolent dec
On Wednesday 16 October 2013 09:48:33 Ben West wrote:
> I noticed that my build tree for AA r38347 only produces the
> openwrt-ar71xx-generic-om2p-squashfs-factory.bin image for Open Mesh OM2P,
> not the sysupgrade image.
>
> The wiki page suggests these images are to be manually flashed to the
>
Hi,
> This is the wiki page in question:
> http://wiki.openwrt.org/toh/openmesh/om2p#upgrading.openwrt
>
> Thank you for clarifying that sysupgrade does work!
if the sysupgrade works to your satisfaction would you mind updating that
section in the wiki ? It might spare the next person some has
On Thursday, May 24, 2012 03:28:43 ZioPRoTo (Saverio Proto) wrote:
> Looks like the committer for the OpenWRT package is Marek:
> https://dev.openwrt.org/browser/packages/net/batman-adv
>
> did you report this problem to him ?
Yes, he did and I told him that mixing trunk packages with stable is n
Hi,
> I already wrote to http://www.open-mesh.org/wiki/open-mesh/MailingList
> (the mailing list of batman-adv routing protocol) but the developers
> of the batman-adv said to me, after some chat and replies, that this
> issue could be solved asking in the openwrt forum, because they didn't
> kno
On Thursday, May 24, 2012 05:53:51 Pedro Nuno Costa Rodrigues wrote:
> I really must done a job and i really need some light in this issue.
> I'm having a good openwrt+batman-adv experience and i'm enjoying a lot.
>
> It seems there is a bug... i must wait a new release, thats right?
No release i
On Thursday, May 24, 2012 16:20:47 ZioPRoTo (Saverio Proto) wrote:
> Marek may I ask if the matter is just this bug with the start/stop
> scripts not working correctly at boot, or if there are more issues in
> using the batman-adv package with the backfire branch ?
The problem arises only if you h
On Friday 09 May 2014 14:11:32 Karl Palsson wrote:
> I understand how it works in general, John was nacking the support as it
> duplicated existing functionality. I was asking more about this existing
> functionality within openwrt for supporting dual firmware images. I wasn't
> aware of any exis
On Saturday 10 May 2014 16:38:42 Karl P wrote:
> On 05/10/2014 10:53 AM, Marek Lindner wrote:
> > On Friday 09 May 2014 14:11:32 Karl Palsson wrote:
> >> I understand how it works in general, John was nacking the support as it
> >> duplicated existing functionality. I
Signed-off-by: Marek Lindner
---
--- a/target/linux/atheros/patches-2.6.37/110-ar2313_ethernet.patch
(revision 27448)
+++ b/target/linux/atheros/patches-2.6.37/110-ar2313_ethernet.patch
(working copy)
@@ -1198,7 +1198,7 @@
+ case SIOCGMIIPHY:
+ case SIOCGMIIREG
On Wednesday, September 14, 2011 15:16:31 Daniel Golle wrote:
> +--- a/drivers/net/wireless/ath/ath9k/ar9002_calib.c
> b/drivers/net/wireless/ath/ath9k/ar9002_calib.c
> +@@ -564,7 +564,7 @@ static inline void ar9285_hw_pa_cal(stru
> +
> + /* PA CAL is not needed for high power solution */
Hi folks,
being a regular user of the combined image I'd like to propose changing the
format in order to render it more flexible. The main focus are the embedded
files: The new format shall be able to embedded numerous files and their
filenames. Furthermore, the type field shall make the image
Hi,
> being a regular user of the combined image I'd like to propose changing
> the format in order to render it more flexible. The main focus are the
> embedded files: The new format shall be able to embedded numerous files
> and their filenames. Furthermore, the type field shall make the image
Nth file (32 bytes)
## version history
# * version 1: initial file format with num files / name / length / md5
checksum
Regards,
Marek
scripts: add script to generate combined extended image format
Signed-off-by: Marek Lindner
---
--- /dev/null
+++ b/scripts/combined-ext-image.sh
@@ -0,0
Hey,
> This patch is an update of http://patchwork.openwrt.org/patch/1452/
>
> The update makes sure that the kernel config actually enables gpio sysfs,
> not just provides support for it. So, as well as the patch, it includes a
> diff on the default config for atheros. The patch itself is un
Hi,
when I upgraded my trunk to a fairly recent version (rev. 29333) I noticed
wifi became practically unusable on my AR9285 device. I spend a good deal of
the day bisecting the recent ath9k changes to identify the culprit:
43c3528430bd29f5e5243. I tried verious things like setting the antenna
On Friday, December 02, 2011 15:31:43 Felix Fietkau wrote:
> > when I upgraded my trunk to a fairly recent version (rev. 29333) I
> > noticed wifi became practically unusable on my AR9285 device. I spend a
> > good deal of the day bisecting the recent ath9k changes to identify the
> > culprit: 43c3
On Friday, December 02, 2011 16:57:19 Felix Fietkau wrote:
> > iw phy phy0 set antenna 1 2
> > command failed: Invalid argument (-22)
> >
> > Maybe the command is incomplete ?
>
> When you run iw phy0 info, what does it show under "Available Antennas"?
iw phy0 info:
Available Antennas: TX 0 RX 0
On Friday, December 02, 2011 17:05:01 Felix Fietkau wrote:
> > Out of curiosity: Since ath9k works without your patch what makes you
> > think it is an EEPROM problem ? Before your patch came there was only
> > the EEPROM setting and nothing else.
>
> Since I didn't have all information yet, I've
On Friday, December 02, 2011 17:51:48 Felix Fietkau wrote:
> Actually, now that I think about it, I can't come up with any lilely
> scenario with my patches where the available antennas would show up as 0
> for tx and rx. Are you sure you gave me this info when running a driver
> without your rever
On Saturday, December 03, 2011 17:31:24 Felix Fietkau wrote:
> > root@OpenWrt:/# iw phy phy0 set antenna 1 2
> > command failed: Invalid argument (-22)
> > root@OpenWrt:/# iw phy phy0 set antenna 1 1
> > command failed: Operation not supported (-122)
>
> Please try the attached patch.
That fixes
On Tuesday, December 20, 2011 23:49:46 Antonio Quartulli wrote:
> om2p-watchdog package is OM2P specific. However a similar watchdog
> mechanism exists on OM1P as well. This new package wants to substitute
> om2p-watchdog with a new one which is suitable either for OM1P and OM2P.
Could you please
it works for them, so might want to give it a try and/or commit it.
Signed-off-by: Marek Lindner
==
--- a/ath/if_ath.c 2009-09-13 00:04:02.0 +0800
+++ b/ath/if_ath.c 2009-09-13 00:04:02.0 +0800
@@ -2781,13 +2785,14
On Thursday 17 September 2009 02:19:57 Felix Fietkau wrote:
> This part is actually wrong. It looks to me as if this 'fixes' a race
> condition by disabling calibration altogether.
I appreciate the feedback but I'm not sure I can follow you here.
The state of the calibration timer is modified in
case. This (ugly)
workaround always sets the first byte to zero to support all
mac addresses.
Signed-off-by: Marek Lindner
---
--- a/ath/if_ath.c 2010-07-13 22:33:42.0 +0200
+++ b/ath/if_ath.c 2010-07-13 22:33:12.0 +0200
@@ -586,7 +586,7 @@
int error = 0
On Thursday 28 April 2011 23:30:32 Felix Fietkau wrote:
> On 2011-04-27 5:50 PM, Marek Lindner wrote:
> > The madwifi driver uses the first byte of the wifi mac address
> > for its VAP mechanism: Each VAP is assigned another value for
> > the first byte to distinguish the tr
vmlinux.bin.l7 being the first partition and use its
address to calculate the size and offset which ultimately leads to a broken
partition table.
This patch alters the behavior by checking what partition has the smaller
address to do the calculations based on that address.
Signed-off-by: Marek
Hi,
the attached patch addresses the disfunctional gpioctl utility which relies on
the gpio_dev module. It has to be put into the
target/linux/generic/patches-$(kernel-version)/ folder for all kernels newer
than 2.6.36. Once this is applied the ticket #9198 can be closed.
Cheers,
Marek
--- a/
On Tuesday, 25. March 2008 03:33:35 Acinonyx wrote:
> This patch (hopefully) fixes batman and batman-advanced compile on 2.6.24
> kernel.
This is fixed upstream since revision 989.
Regards,
Marek
___
openwrt-devel mailing list
openwrt-devel@lists.openw
35 matches
Mail list logo
