* [ath9k-devel] [PATCH 2/2] ath9k: index out of bounds
From: roel @ 2011-04-10 19:09 UTC (permalink / raw)
To: ath9k-devel
Check whether index is within bounds before testing the element
Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
---
drivers/net/wireless/ath/ath9k/rc.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/rc.c b/drivers/net/wireless/ath/ath9k/rc.c
index 4c0d36a..1809409 100644
--- a/drivers/net/wireless/ath/ath9k/rc.c
+++ b/drivers/net/wireless/ath/ath9k/rc.c
@@ -1092,8 +1092,7 @@ static int ath_rc_get_rateindex(const struct ath_rate_table *rate_table,
if (!(rate->flags & IEEE80211_TX_RC_MCS))
return rate->idx;
- while (rate->idx > mcs_rix_off[i] &&
- i < ARRAY_SIZE(mcs_rix_off)) {
+ while (i < ARRAY_SIZE(mcs_rix_off) && rate->idx > mcs_rix_off[i]) {
rix++; i++;
}
^ permalink raw reply related
* [PATCH 1/2] ath9k_hw: index out of bounds
From: roel @ 2011-04-10 19:09 UTC (permalink / raw)
To: Luis R. Rodriguez, Jouni Malinen, Vasanthakumar Thiagarajan,
Senthil Balasubramanian, linux-wireless, ath9k-devel,
Andrew Morton, LKML
Check whether index is within bounds before testing the element
Both spurChans arrays in modalHeader5G and modalHeader2G have 5 elements,
AR_EEPROM_MODAL_SPURS is defined 5. So unless a break occurs, in the
last iteration (i=5) we tried to access spurChansPtr[5] before testing
whether i was within bounds. Fix this.
Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
---
drivers/net/wireless/ath/ath9k/ar9003_phy.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_phy.c b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
index eb250d6..93398de 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_phy.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
@@ -401,7 +401,7 @@ static void ar9003_hw_spur_mitigate_ofdm(struct ath_hw *ah,
ar9003_hw_spur_ofdm_clear(ah);
- for (i = 0; spurChansPtr[i] && i < 5; i++) {
+ for (i = 0; i < AR_EEPROM_MODAL_SPURS && spurChansPtr[i]; i++) {
freq_offset = FBIN2FREQ(spurChansPtr[i], mode) - synth_freq;
if (abs(freq_offset) < range) {
ar9003_hw_spur_ofdm_work(ah, chan, freq_offset);
^ permalink raw reply related
* [PATCH 1/2] ath9k_hw: index out of bounds
From: roel @ 2011-04-10 19:09 UTC (permalink / raw)
To: Luis R. Rodriguez, Jouni Malinen, Vasanthakumar Thiagarajan,
Senthil Balasubramanian, linux-wireless, ath9k-devel,
Andrew Morton, LKML
Check whether index is within bounds before testing the element
Both spurChans arrays in modalHeader5G and modalHeader2G have 5 elements,
AR_EEPROM_MODAL_SPURS is defined 5. So unless a break occurs, in the
last iteration (i=5) we tried to access spurChansPtr[5] before testing
whether i was within bounds. Fix this.
Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
---
drivers/net/wireless/ath/ath9k/ar9003_phy.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_phy.c b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
index eb250d6..93398de 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_phy.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
@@ -401,7 +401,7 @@ static void ar9003_hw_spur_mitigate_ofdm(struct ath_hw *ah,
ar9003_hw_spur_ofdm_clear(ah);
- for (i = 0; spurChansPtr[i] && i < 5; i++) {
+ for (i = 0; i < AR_EEPROM_MODAL_SPURS && spurChansPtr[i]; i++) {
freq_offset = FBIN2FREQ(spurChansPtr[i], mode) - synth_freq;
if (abs(freq_offset) < range) {
ar9003_hw_spur_ofdm_work(ah, chan, freq_offset);
^ permalink raw reply related
* [ath9k-devel] [PATCH 1/2] ath9k_hw: index out of bounds
From: roel @ 2011-04-10 19:09 UTC (permalink / raw)
To: ath9k-devel
Check whether index is within bounds before testing the element
Both spurChans arrays in modalHeader5G and modalHeader2G have 5 elements,
AR_EEPROM_MODAL_SPURS is defined 5. So unless a break occurs, in the
last iteration (i=5) we tried to access spurChansPtr[5] before testing
whether i was within bounds. Fix this.
Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
---
drivers/net/wireless/ath/ath9k/ar9003_phy.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/ar9003_phy.c b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
index eb250d6..93398de 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_phy.c
+++ b/drivers/net/wireless/ath/ath9k/ar9003_phy.c
@@ -401,7 +401,7 @@ static void ar9003_hw_spur_mitigate_ofdm(struct ath_hw *ah,
ar9003_hw_spur_ofdm_clear(ah);
- for (i = 0; spurChansPtr[i] && i < 5; i++) {
+ for (i = 0; i < AR_EEPROM_MODAL_SPURS && spurChansPtr[i]; i++) {
freq_offset = FBIN2FREQ(spurChansPtr[i], mode) - synth_freq;
if (abs(freq_offset) < range) {
ar9003_hw_spur_ofdm_work(ah, chan, freq_offset);
^ permalink raw reply related
* [U-Boot] Please pull u-boot-cfi-flash
From: Wolfgang Denk @ 2011-04-10 19:05 UTC (permalink / raw)
To: u-boot
In-Reply-To: <201104071025.32882.sr@denx.de>
Dear Stefan Roese,
In message <201104071025.32882.sr@denx.de> you wrote:
> Hi Wolfgang,
>
> please pull the following changes:
>
> The following changes since commit 4db2fa7f9446d0f2fe8db3d62184b1212fe22707:
>
> Merge branch 'master' of git://git.denx.de/u-boot-mpc85xx (2011-04-05 12:24:20 +0200)
>
> are available in the git repository at:
>
> git://www.denx.de/git/u-boot-cfi-flash.git master
>
> Heiko Schocher (1):
> mtd, cfi: introduce void flash_protect_default(void)
>
> Mario Schuknecht (1):
> cfi_flash: use AMD fixups for AMIC (e.g. A29L160A series) too
>
> drivers/mtd/cfi_flash.c | 80 +++++++++++++++++++++++++---------------------
> include/flash.h | 1 +
> 2 files changed, 44 insertions(+), 37 deletions(-)
Applied, thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The project was large enough and management communication poor enough
to prompt many members of the team to see themselves as contestants
making brownie points, rather than as builders making programming
products. Each suboptimized his piece to meet his targets; few
stopped to think about the total effect on the customer.
- Fred Brooks, "The Mythical Man Month"
^ permalink raw reply
* Re: Firmware files for Ralink RT28x0
From: Ben Hutchings @ 2011-04-10 19:04 UTC (permalink / raw)
To: Ivo Van Doorn; +Cc: Gertjan van Wingerde, linux-wireless
In-Reply-To: <BANLkTi=o3P7PbcjW1n_dnhtwX08UE4t2+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]
On Sun, 2011-04-10 at 20:06 +0200, Ivo Van Doorn wrote:
> Hi,
>
> >> On Sun, Apr 10, 2011 at 5:56 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> >> > I notice that rt2800{pci,usb} each specify only one firmware image,
> >> > regardless of the controller version.
> >> >
> >> > This is inconsistent with rt28{6,7}0sta and with the firmware images in
> >> > linux-firmware.
> >>
> >> Well the rt2800pci/usb firmware behavior is consistent with the original
> >> Ralink drivers (Not sure about the staging drivers, I only look to the drivers
> >> on the Ralink website).
> >
> > Are you referring to the #ifdef BIN_IN_FILE code? This code is not
> > enabled, so you should assume it is broken. I suspect that it was
> > intended to ease firmware development.
>
> Not only BIN_IN_FILE, but the .bin files provided in the Ralink package
> itself. At some point I grabbed all .bin files from all Ralink packages,
> and compared them.
But this proves nothing, because the Ralink drivers don't use those
files!
[...]
> > The firmware blobs in RT2870 version 2009-08-20 and RT3070 version
> > 2009-05-25 are all marked as version 17 (or 0.17), but *they all have
> > different contents*.
>
> How do you determine this version? I usually check the last couple
> of bytes of the firmware file. (The last 2 bytes of the firmware is the CRC,
> but the 2 bytes before that is the version).
That's exactly what I'm looking at, in the file include/firmware.h.
There are 256 lines * 16 bytes for each image, so the images end with:
RT2870 image 1: 0x00, 0x11, 0xc2, 0x7a
RT2870 image 2: 0x00, 0x11, 0x77, 0x81
RT3070 image 1: 0x00, 0x11, 0x7b, 0xc4
RT3070 image 2: 0x00, 0x11, 0x65, 0xd3
By the way, there is a comment in common/rtmp_mcu.c which says the
version number for these chips is only 1 byte.
[...]
> > linux-firmware is supposed to have all firmware files referenced by any
--- ---
> > version of Linux; therefore these files must not be removed.
>
> I agree that the firmware should be in linux-firmware, but only if they
> are the latest version (and it is possible to keep them up-to-date). Having
> outdated firmware in the linux-firmware tree only causes more problems.
>
> > If just two files are sufficient then the other files could be replaced
> > by symlinks to them.
>
> Why? The patch to remove the staging drivers has been sent out a few
> days ago. After that we only have rt2800pci and rt2800usb drivers,
> so we can get rid of the rt30xx files completely. ;)
No. Read what I said again.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply
* Compat-wireless release for 2011-04-10 is baked
From: Compat-wireless cronjob account @ 2011-04-10 19:02 UTC (permalink / raw)
To: linux-wireless
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
cat: compat_base_tree: No such file or directory
cat: compat_base_tree_version: No such file or directory
cat: compat_version: No such file or directory
cat: /var/opt/compat/compat-wireless-2.6/compat_version: No such file or directory
scripts/Makefile.clean:17: /var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile: No such file or directory
make[4]: *** No rule to make target `/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap/Makefile'. Stop.
make[3]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless/hostap] Error 2
make[2]: *** [/var/opt/compat/compat-wireless-2.6/drivers/net/wireless] Error 2
make[1]: *** [_clean_/var/opt/compat/compat-wireless-2.6] Error 2
make: *** [clean] Error 2
/usr/bin/sha1sum: *.tar.bz2: No such file or directory
compat-wireless code metrics
837893 - Total upstream lines of code being pulled
^ permalink raw reply
* load balanced between tunnel VPN and an Normal Link Internet
From: Usuário do Sistema @ 2011-04-10 18:55 UTC (permalink / raw)
To: netfilter
disregard my previous menssage because it's was without subject
Hello everyone, I'm new in this maillist and I would like receive help
about my problem......
I have a Firewall ( with fwbuider - Red-Hat 5.6 ) in my branch office
connected to my head office by openvpn. I'm with a problem when flow
data is to destination port 80 from my branch office to my head
office.
in my branch office firewall has 3 device Ethernet:
eth0 - inside network 192.100.100.0/24
eth1 - wan 1 VPN
eth2 - wan 2 only for Internet Traffic
I'm marking all traffic for port 80 go out upon wan 2 - eth2. but,
it's a problem because when an user tries access an service at the
port 80 in my head office it isen't work!
the firewall toward to eth2 insted to VPN the traffic from inside
network to my head office when destinatio is port 80. I've try solve
this with rule below but it isen't work.occur the same problem.
my head office inside network is 128.2.0.0/16 where I have my web
servers at the port 80.
rules created in firewall branch office
/sbin/iptables -t mangle -A PREROUTING -s 0/0 -d ! 128.2.0.0/16 -p tcp
--dport 80 -j MARK --set-mark 1
ip rule del fwmark 1
ip route flush table internet
ip rule add fwmark 1 table internet prio 20
ip route add default via 200.108.139.1 table internet ( it's eth2 )
ip route flush cache
part from my route main table
128.2.0.0 192.168.200.101 255.255.0.0 UG 0 0 0 tun0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth3
0.0.0.0 190.128.173.97 0.0.0.0 UG 0 0
0 eth1 > where is my VPN
any Tip ?? I wish that packages from inside networ 192.100.100.0/24 to
128.2.0.0/16 port 80 go out for tun0 insted by eth2
^ permalink raw reply
* Re: [PATCH] net: sky2: convert to hw_features
From: Stephen Hemminger @ 2011-04-10 18:53 UTC (permalink / raw)
To: Michał Mirosław; +Cc: netdev
In-Reply-To: <20110410131321.8CD9713A64@rere.qmqm.pl>
On Sun, 10 Apr 2011 15:13:21 +0200 (CEST)
Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:
> Caveats:
> - driver modifies vlan_features on HW VLAN TX changes
> - broken RX checksum will be reenabled on features change
>
To be more precise. This is acceptable if and only if all cases
where features are disabled in response to MTU and chip versions
are exactly the same. We don't want to let some user stumble upon
cases where hardware features don't work in their configuration.
--
^ permalink raw reply
* Re: [Qemu-devel] tcg/tcg.c:1892: tcg fatal error
From: Igor Kovalenko @ 2011-04-10 18:52 UTC (permalink / raw)
To: Artyom Tarasenko; +Cc: Blue Swirl, peter.maydell, qemu-devel, Aurelien Jarno
In-Reply-To: <BANLkTikgtE-Nn4JJFYUA+OWwjgc2qBixMw@mail.gmail.com>
On Sun, Apr 10, 2011 at 10:35 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
> On Sun, Apr 10, 2011 at 7:57 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Sun, Apr 10, 2011 at 8:48 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
>>> On Sun, Apr 10, 2011 at 4:44 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>>>> On Sun, Apr 10, 2011 at 5:09 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
>>>>> On Sun, Apr 10, 2011 at 3:24 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>>>>>> On Sun, Apr 10, 2011 at 02:29:59PM +0200, Artyom Tarasenko wrote:
>>>>>>> Trying to boot some proprietary OS I get qemu-system-sparc64 crash with a
>>>>>>>
>>>>>>> tcg/tcg.c:1892: tcg fatal error
>>>>>>>
>>>>>>> error message.
>>>>>>>
>>>>>>> It looks like it can be a platform independent bug though, because
>>>>>>> when a '-singlestep' option IS present, qemu doesn't crash and seems
>>>>>>> to translate the code properly.
>>>>>>>
>>>>>>> (gdb) bt
>>>>>>> #0 0x00000032c2e327f5 in raise () from /lib64/libc.so.6
>>>>>>> #1 0x00000032c2e33fd5 in abort () from /lib64/libc.so.6
>>>>>>> #2 0x000000000051933d in tcg_reg_alloc_call (s=<value optimized out>,
>>>>>>> def=0x89d340, opc=INDEX_op_call, args=0x10acc98, dead_iargs=3) at
>>>>>>> qemu/tcg/tcg.c:1892
>>>>>>> #3 0x000000000051a557 in tcg_gen_code_common (s=0x10b8940,
>>>>>>> gen_code_buf=0x40338b60 "I\213n@H\213] 3\355I\211\256\220") at
>>>>>>> qemu/tcg/tcg.c:2099
>>>>>>> #4 tcg_gen_code (s=0x10b8940, gen_code_buf=0x40338b60 "I\213n@H\213]
>>>>>>> 3\355I\211\256\220") at qemu/tcg/tcg.c:2142
>>>>>>> #5 0x00000000004d38f1 in cpu_sparc_gen_code (env=0x10cce10,
>>>>>>> tb=0x7fffe91bc218, gen_code_size_ptr=0x7fffffffd9b4) at
>>>>>>> qemu/translate-all.c:93
>>>>>>> #6 0x00000000004d1fd7 in tb_gen_code (env=0x10cce10, pc=18868776,
>>>>>>> cs_base=18868780, flags=15, cflags=0) at qemu/exec.c:989
>>>>>>> #7 0x00000000004d4029 in tb_find_slow (env1=<value optimized out>) at
>>>>>>> qemu/cpu-exec.c:167
>>>>>>> #8 tb_find_fast (env1=<value optimized out>) at cpu-exec.c:194
>>>>>>> #9 cpu_sparc_exec (env1=<value optimized out>) at qemu/cpu-exec.c:556
>>>>>>> #10 0x0000000000408868 in tcg_cpu_exec () at qemu/cpus.c:1066
>>>>>>> #11 cpu_exec_all () at qemu/cpus.c:1102
>>>>>>> #12 0x000000000053c756 in main_loop (argc=<value optimized out>,
>>>>>>> argv=<value optimized out>, envp=<value optimized out>) at
>>>>>>> qemu/vl.c:1430
>>>>>>>
>>>>>>> I inspected ts->val_type causing the abort() case and it turned out to be 0.
>>>>>>>
>>>>>>> The last lines of qemu.log (without -singlestep)
>>>>>>> IN:
>>>>>>> 0x00000000011fe9f0: rdpr %pstate, %g1
>>>>>>> 0x00000000011fe9f4: wrpr %g1, 2, %pstate
>>>>>>> --------------
>>>>>>> IN:
>>>>>>> 0x00000000011fe9f8: ldub [ %o0 ], %o1
>>>>>>> 0x00000000011fe9fc: mov %o1, %o2
>>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>>>
>>>>>>> Search PC...
>>>>>>> Search PC...
>>>>>>> Search PC...
>>>>>>> Search PC...
>>>>>>> Search PC...
>>>>>>> Search PC...
>>>>>>> --------------
>>>>>>> IN:
>>>>>>> 0x00000000011fe9f8: ldub [ %o0 ], %o1
>>>>>>> 0x00000000011fe9fc: mov %o1, %o2
>>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>>>
>>>>>>> 110521: Data Access MMU Miss (v=0068) pc=00000000011fe9f8
>>>>>>> npc=00000000011fe9fc SP=000000000180ae41
>>>>>>> pc: 00000000011fe9f8 npc: 00000000011fe9fc
>>>>>>>
>>>>>>> IN:
>>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>>> --------------
>>>>>>> IN:
>>>>>>> 0x00000000011fea10: brz,pn %o2, 0x11fe9f8
>>>>>>> 0x00000000011fea14: mov %o2, %o4
>>>>>>> --------------
>>>>>>> IN:
>>>>>>> 0x00000000011fea18: rdpr %tick, %o5
>>>>>>> 0x00000000011fea1c: cmp %o2, %o4
>>>>>>> 0x00000000011fea20: be %icc, 0x11fea18
>>>>>>> 0x00000000011fea24: ldub [ %o0 ], %o4
>>>>>>> --------------
>>>>>>> IN:
>>>>>>> 0x00000000011fea28: brz,pn %o4, 0x11fe9f4
>>>>>>> 0x00000000011fea2c: wrpr %g0, %g1, %pstate
>>>>>>> <EOF>
>>>>>>>
>>>>>>> The crash is 100% reproducible and happens always on the same place,
>>>>>>> so it's probably a pure TCG issue, not related on getting the
>>>>>>> external/timer interrupts.
>>>>>>>
>>>>>>> Do you need any additional info?
>>>>>>>
>>>>>>
>>>>>> What would be interesting would be to get the corresponding TCG code
>>>>>> from qemu.log (-d op,op_opt).
>>>>>
>>>>>
>>>>> OP:
>>>>> ---- 0x11fea28
>>>>> ld_i64 tmp6,regwptr,$0x20
>>>>> movi_i64 cond,$0x0
>>>>> movi_i64 tmp8,$0x0
>>>>> brcond_i64 tmp6,tmp8,ne,$0x0
>>>>> movi_i64 cond,$0x1
>>>>> set_label $0x0
>>>>>
>>>>> ---- 0x11fea2c
>>>>> movi_i64 tmp7,$0x0
>>>>> xor_i64 tmp0,tmp7,g1
>>>>> movi_i64 pc,$0x11fea2c
>>>>> movi_i64 tmp8,$compute_psr
>>>>> call tmp8,$0x0,$0
>>>>> movi_i64 tmp8,$0x0
>>>>> brcond_i64 cond,tmp8,eq,$0x1
>>>>> movi_i64 npc,$0x11fe9f4
>>>>> br $0x2
>>>>> set_label $0x1
>>>>> movi_i64 npc,$0x11fea30
>>>>> set_label $0x2
>>>>> movi_i64 tmp8,$wrpstate
>>>>> call tmp8,$0x0,$0,tmp0
>>>>> mov_i64 pc,npc
>>>>> movi_i64 tmp8,$0x4
>>>>> add_i64 npc,npc,tmp8
>>>>> exit_tb $0x0
>>>>>
>>>>> OP after liveness analysis:
>>>>> ---- 0x11fea28
>>>>> ld_i64 tmp6,regwptr,$0x20
>>>>> movi_i64 cond,$0x0
>>>>> movi_i64 tmp8,$0x0
>>>>> brcond_i64 tmp6,tmp8,ne,$0x0
>>>>> movi_i64 cond,$0x1
>>>>> set_label $0x0
>>>>>
>>>>> ---- 0x11fea2c
>>>>> nopn $0x2,$0x2
>>>>> nopn $0x3,$0x68,$0x3
>>>>> movi_i64 pc,$0x11fea2c
>>>>> movi_i64 tmp8,$compute_psr
>>>>> call tmp8,$0x0,$0
>>>>> movi_i64 tmp8,$0x0
>>>>> brcond_i64 cond,tmp8,eq,$0x1
>>>>> movi_i64 npc,$0x11fe9f4
>>>>> br $0x2
>>>>> set_label $0x1
>>>>> movi_i64 npc,$0x11fea30
>>>>> set_label $0x2
>>>>> movi_i64 tmp8,$wrpstate
>>>>> call tmp8,$0x0,$0,tmp0
>>>>> mov_i64 pc,npc
>>>>> movi_i64 tmp8,$0x4
>>>>> add_i64 npc,npc,tmp8
>>>>> exit_tb $0x0
>>>>> end
>>>>>
>>>>> Does it mean the last block is processed correctly and the crash
>>>>> happens on the next instruction which doesn't make it to the log?
>>>>> The next instruction would be a
>>>>>
>>>>> 0x00000000011fea30: retl
>>>>>
>>>>> Since it's a branch instruction I guess this would also be a tcg block boundary.
>>>>
>>>> Because abort() was called from tcg_reg_alloc_call, I'd say 'retl'
>>>> (synthetic op for 'jmpl %o8 + 8, %g0') was the problem.
>>>
>>> Any idea why? retl is not a rare instruction...
>>
>> Sorry, calls are generated for helpers, so it's not 'jmpl' but the
>> call to wrpstate helper.
>
> And why it doesn't happen in a singlestep mode?
> I tried to comment out
> cpu_check_irqs(env);
> in the helper_wrpstate but it made no difference. The only suspicious
> thing left is register bank switching. Is it safe to switch register
> banks in the helper function? Shouldn't we end the translation block
> before?
>
> --
> Regards,
> Artyom Tarasenko
>
> solaris/sparc under qemu blog: http://tyom.blogspot.com/
>
>
Not sure if I have seen write to pstate in delay slot, but switching
globals with PS_AG appears to be safe.
Do you know which bits are changed in the pstate?
--
Kind regards,
Igor V. Kovalenko
^ permalink raw reply
* Re: What's cooking in git.git (Apr 2011, #02; Wed, 6)
From: Ævar Arnfjörð Bjarmason @ 2011-04-10 18:52 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git, Jens Lehmann
In-Reply-To: <7v8vvni1t3.fsf@alter.siamese.dyndns.org>
On Wed, Apr 6, 2011 at 22:04, Junio C Hamano <gitster@pobox.com> wrote:
> * jl/submodule-fetch-on-demand (2011-03-06) 7 commits
> (merged to 'next' on 2011-03-20 at a5e452d)
> + fetch/pull: Describe --recurse-submodule restrictions in the BUGS section
> + submodule update: Don't fetch when the submodule commit is already present
> + fetch/pull: Don't recurse into a submodule when commits are already present
> + Submodules: Add 'on-demand' value for the 'fetchRecurseSubmodule' option
> + config: teach the fetch.recurseSubmodules option the 'on-demand' value
> + fetch/pull: Add the 'on-demand' value to the --recurse-submodules option
> + fetch/pull: recurse into submodules when necessary
This series needs to be fixed to not fail tests with GETTEXT_POISON=YesPlease.
^ permalink raw reply
* Re: [PATCH] net: sky2: convert to hw_features
From: Stephen Hemminger @ 2011-04-10 18:49 UTC (permalink / raw)
To: Michał Mirosław; +Cc: netdev
In-Reply-To: <20110410131321.8CD9713A64@rere.qmqm.pl>
On Sun, 10 Apr 2011 15:13:21 +0200 (CEST)
Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:
> Caveats:
> - driver modifies vlan_features on HW VLAN TX changes
> - broken RX checksum will be reenabled on features change
This seems unsafe.
^ permalink raw reply
* Re: [RFC V2 01/21]arch:arm:mach Remove extra semi-colon.
From: Justin P. Mattock @ 2011-04-10 18:49 UTC (permalink / raw)
To: Jiri Kosina; +Cc: linux-kernel
In-Reply-To: <alpine.LNX.2.00.1104081949580.6392@deuxcents.site>
On 04/10/2011 08:09 AM, Jiri Kosina wrote:
> On Thu, 24 Mar 2011, Justin P. Mattock wrote:
>
>> The patch below removes an extra semi-colon from various parts
>> of the kernel.
>
> I have folded all the patches into one and applied.
>
alright..
as for the other ones I can go and check to see, then resend if need be.
Justin P. Mattock
^ permalink raw reply
* Re: [PATCH] MINIX file system version 3 support
From: Vladimir 'φ-coder/phcoder' Serbinenko @ 2011-04-10 18:39 UTC (permalink / raw)
To: The development of GNU GRUB; +Cc: Fam Zheng
In-Reply-To: <AANLkTik2U7FRO=+Wy9R9PFakOdeNG7Xftoor=gxXPGPe@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]
On 28.07.2010 05:25, Fam Zheng wrote:
> Hi,
>
> To support MINIX file system version 3, this patch adds a new module
> named 'minix3'. It reuses most of the code in minix.mod, and handles
> the latest MINIX file system version 3.
>
I've cleaned it up. Could you test it and point me as to where I can get
an minix3 image for my own tests?
> The requested assignment information has also been sent to
> assign@gnu.org <mailto:assign@gnu.org>.
>
> --
> Best Regards!
> Fam Zheng
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: minix3.diff --]
[-- Type: text/x-diff; name="minix3.diff", Size: 10373 bytes --]
=== modified file 'grub-core/Makefile.core.def'
--- grub-core/Makefile.core.def 2011-03-26 11:59:02 +0000
+++ grub-core/Makefile.core.def 2011-04-10 15:36:48 +0000
@@ -959,6 +959,11 @@
};
module = {
+ name = minix3;
+ common = fs/minix3.c;
+};
+
+module = {
name = nilfs2;
common = fs/nilfs2.c;
};
=== modified file 'grub-core/fs/minix.c'
--- grub-core/fs/minix.c 2010-10-16 20:16:52 +0000
+++ grub-core/fs/minix.c 2011-04-10 16:35:06 +0000
@@ -25,14 +25,17 @@
#include <grub/dl.h>
#include <grub/types.h>
-#ifdef MODE_MINIX2
+#ifdef MODE_MINIX3
+#define GRUB_MINIX_MAGIC 0x4D5A
+#elif defined(MODE_MINIX2)
#define GRUB_MINIX_MAGIC 0x2468
#define GRUB_MINIX_MAGIC_30 0x2478
#else
#define GRUB_MINIX_MAGIC 0x137F
#define GRUB_MINIX_MAGIC_30 0x138F
#endif
-#define GRUB_MINIX_BSIZE 1024U
+
+#define GRUB_MINIX_INODE_DIR_BLOCKS 7
#define GRUB_MINIX_LOG2_BSIZE 1
#define GRUB_MINIX_ROOT_INODE 1
#define GRUB_MINIX_MAX_SYMLNK_CNT 8
@@ -41,7 +44,7 @@
#define GRUB_MINIX_IFDIR 0040000U
#define GRUB_MINIX_IFLNK 0120000U
-#ifdef MODE_MINIX2
+#if defined(MODE_MINIX2) || defined(MODE_MINIX3)
typedef grub_uint32_t grub_minix_uintn_t;
#define grub_minix_le_to_cpu_n grub_le_to_cpu32
#else
@@ -50,6 +53,13 @@
#endif
#define GRUB_MINIX_INODE_BLKSZ(data) sizeof (grub_minix_uintn_t)
+#ifdef MODE_MINIX3
+typedef grub_uint32_t grub_minix_ino_t;
+#define grub_minix_le_to_cpu_ino grub_le_to_cpu32
+#else
+typedef grub_uint16_t grub_minix_ino_t;
+#define grub_minix_le_to_cpu_ino grub_le_to_cpu16
+#endif
#define GRUB_MINIX_INODE_SIZE(data) (grub_minix_le_to_cpu_n (data->inode.size))
#define GRUB_MINIX_INODE_MODE(data) (grub_le_to_cpu16 (data->inode.mode))
@@ -62,9 +72,28 @@
#define GRUB_MINIX_LOG2_ZONESZ (GRUB_MINIX_LOG2_BSIZE \
+ grub_le_to_cpu16 (sblock->log2_zone_size))
-#define GRUB_MINIX_ZONESZ (GRUB_MINIX_BSIZE \
+#define GRUB_MINIX_ZONESZ (data->block_size \
<< grub_le_to_cpu16 (sblock->log2_zone_size))
+#ifdef MODE_MINIX3
+struct grub_minix_sblock
+{
+ grub_uint32_t inode_cnt;
+ grub_uint16_t zone_cnt;
+ grub_uint16_t inode_bmap_size;
+ grub_uint16_t zone_bmap_size;
+ grub_uint16_t first_data_zone;
+ grub_uint16_t log2_zone_size;
+ grub_uint16_t pad;
+ grub_uint32_t max_file_size;
+ grub_uint32_t zones;
+ grub_uint16_t magic;
+
+ grub_uint16_t pad2;
+ grub_uint16_t block_size;
+ grub_uint8_t disk_version;
+};
+#else
struct grub_minix_sblock
{
grub_uint16_t inode_cnt;
@@ -76,8 +105,28 @@
grub_uint32_t max_file_size;
grub_uint16_t magic;
};
-
-#ifndef MODE_MINIX2
+#endif
+
+#if defined(MODE_MINIX3)
+
+struct grub_minix_inode
+{
+ grub_uint16_t mode;
+ grub_uint16_t nlinks;
+ grub_uint16_t uid;
+ grub_uint8_t gid;
+ grub_uint8_t pad;
+ grub_uint32_t size;
+ grub_uint32_t atime;
+ grub_uint32_t mtime;
+ grub_uint32_t ctime;
+ grub_uint32_t dir_zones[7];
+ grub_uint32_t indir_zone;
+ grub_uint32_t double_indir_zone;
+ grub_uint32_t unused;
+};
+
+#elif defined(MODE_MINIX2)
struct grub_minix_inode
{
grub_uint16_t mode;
@@ -121,6 +170,7 @@
int linknest;
grub_disk_t disk;
int filename_size;
+ grub_size_t block_size;
};
static grub_dl_t my_mod;
@@ -141,18 +191,22 @@
{
grub_minix_uintn_t indirn;
grub_disk_read (data->disk,
+#ifdef MODE_MINIX3
+ zone * (data->block_size / GRUB_DISK_SECTOR_SIZE),
+#else
zone << GRUB_MINIX_LOG2_ZONESZ,
+#endif
sizeof (grub_minix_uintn_t) * num,
sizeof (grub_minix_uintn_t), (char *) &indirn);
return grub_minix_le_to_cpu_n (indirn);
}
/* Direct block. */
- if (blk < 7)
+ if (blk < GRUB_MINIX_INODE_DIR_BLOCKS)
return GRUB_MINIX_INODE_DIR_ZONES (data, blk);
/* Indirect block. */
- blk -= 7;
+ blk -= GRUB_MINIX_INODE_DIR_BLOCKS;
if (blk < GRUB_MINIX_ZONESZ / GRUB_MINIX_INODE_BLKSZ (data))
{
indir = grub_get_indir (GRUB_MINIX_INODE_INDIR_ZONE (data), blk);
@@ -185,25 +239,27 @@
grub_minix_read_file (struct grub_minix_data *data,
void NESTED_FUNC_ATTR (*read_hook) (grub_disk_addr_t sector,
unsigned offset, unsigned length),
- int pos, grub_disk_addr_t len, char *buf)
+ grub_off_t pos, grub_disk_addr_t len, char *buf)
{
struct grub_minix_sblock *sblock = &data->sblock;
- int i;
- int blockcnt;
+ grub_disk_addr_t i;
+ grub_disk_addr_t blockcnt;
+ grub_uint64_t posblock;
+ grub_uint32_t blockoff;
/* Adjust len so it we can't read past the end of the file. */
if (len + pos > GRUB_MINIX_INODE_SIZE (data))
len = GRUB_MINIX_INODE_SIZE (data) - pos;
- blockcnt = (len + pos + GRUB_MINIX_BSIZE - 1) / GRUB_MINIX_BSIZE;
+ blockcnt = grub_divmod64 ((len + pos + data->block_size - 1),
+ data->block_size, 0);
+ posblock = grub_divmod64 (pos, data->block_size, &blockoff);
- for (i = pos / GRUB_MINIX_BSIZE; i < blockcnt; i++)
+ for (i = posblock; i < blockcnt; i++)
{
- int blknr;
- int blockoff = pos % GRUB_MINIX_BSIZE;
- int blockend = GRUB_MINIX_BSIZE;
-
- int skipfirst = 0;
+ grub_disk_addr_t blknr;
+ grub_uint32_t blockend = data->block_size;
+ grub_off_t skipfirst = 0;
blknr = grub_minix_get_file_block (data, i);
if (grub_errno)
@@ -212,28 +268,32 @@
/* Last block. */
if (i == blockcnt - 1)
{
- blockend = (len + pos) % GRUB_MINIX_BSIZE;
+ grub_divmod64 (len + pos, data->block_size, &blockend);
if (!blockend)
- blockend = GRUB_MINIX_BSIZE;
+ blockend = data->block_size;
}
/* First block. */
- if (i == (pos / (int) GRUB_MINIX_BSIZE))
+ if (i == posblock)
{
skipfirst = blockoff;
blockend -= skipfirst;
}
data->disk->read_hook = read_hook;
- grub_disk_read (data->disk, blknr << GRUB_MINIX_LOG2_ZONESZ,
+ grub_disk_read (data->disk,
+#ifdef MODE_MINIX3
+ blknr * (sblock->block_size / GRUB_DISK_SECTOR_SIZE),
+#else
+ blknr << GRUB_MINIX_LOG2_ZONESZ,
+#endif
skipfirst, blockend, buf);
-
data->disk->read_hook = 0;
if (grub_errno)
return -1;
- buf += GRUB_MINIX_BSIZE - skipfirst;
+ buf += data->block_size - skipfirst;
}
return len;
@@ -248,16 +308,18 @@
struct grub_minix_sblock *sblock = &data->sblock;
/* Block in which the inode is stored. */
- int block;
+ grub_disk_addr_t block;
data->ino = ino;
/* The first inode in minix is inode 1. */
ino--;
-
- block = ((2 + grub_le_to_cpu16 (sblock->inode_bmap_size)
- + grub_le_to_cpu16 (sblock->zone_bmap_size))
- << GRUB_MINIX_LOG2_BSIZE);
-
+ block = (2 + grub_le_to_cpu16 (sblock->inode_bmap_size)
+ + grub_le_to_cpu16 (sblock->zone_bmap_size));
+#ifndef MODE_MINIX3
+ block <<= GRUB_MINIX_LOG2_BSIZE;
+#else
+ block *= sblock->block_size / GRUB_DISK_SECTOR_SIZE;
+#endif
block += ino / (GRUB_DISK_SECTOR_SIZE / sizeof (struct grub_minix_inode));
int offs = (ino % (GRUB_DISK_SECTOR_SIZE
/ sizeof (struct grub_minix_inode))
@@ -333,7 +395,7 @@
do
{
- grub_uint16_t ino;
+ grub_minix_ino_t ino;
char filename[data->filename_size + 1];
if (grub_strlen (name) == 0)
@@ -353,7 +415,7 @@
if (!grub_strcmp (name, filename))
{
dirino = data->ino;
- grub_minix_read_inode (data, grub_le_to_cpu16 (ino));
+ grub_minix_read_inode (data, grub_minix_le_to_cpu_ino (ino));
/* Follow the symlink. */
if ((GRUB_MINIX_INODE_MODE (data)
@@ -409,20 +471,35 @@
goto fail;
if (grub_le_to_cpu16 (data->sblock.magic) == GRUB_MINIX_MAGIC)
+ {
+#if !defined(MODE_MINIX3)
data->filename_size = 14;
+#else
+ data->filename_size = 60;
+#endif
+ }
+#if !defined(MODE_MINIX3)
else if (grub_le_to_cpu16 (data->sblock.magic) == GRUB_MINIX_MAGIC_30)
data->filename_size = 30;
+#endif
else
goto fail;
data->disk = disk;
data->linknest = 0;
+#ifdef MODE_MINIX3
+ data->block_size = grub_le_to_cpu16 (data->sblock.block_size);
+#else
+ data->block_size = 1024U;
+#endif
return data;
fail:
grub_free (data);
-#ifdef MODE_MINIX2
+#if defined(MODE_MINIX3)
+ grub_error (GRUB_ERR_BAD_FS, "not a minix3 filesystem");
+#elif defined(MODE_MINIX2)
grub_error (GRUB_ERR_BAD_FS, "not a minix2 filesystem");
#else
grub_error (GRUB_ERR_BAD_FS, "not a minix filesystem");
@@ -458,7 +535,7 @@
while (pos < GRUB_MINIX_INODE_SIZE (data))
{
- grub_uint16_t ino;
+ grub_minix_ino_t ino;
char filename[data->filename_size + 1];
int dirino = data->ino;
struct grub_dirhook_info info;
@@ -474,10 +551,13 @@
(char *) filename) < 0)
return grub_errno;
filename[data->filename_size] = '\0';
+ if (!ino)
+ {
+ pos += sizeof (ino) + data->filename_size;
+ continue;
+ }
- /* The filetype is not stored in the dirent. Read the inode to
- find out the filetype. This *REALLY* sucks. */
- grub_minix_read_inode (data, grub_le_to_cpu16 (ino));
+ grub_minix_read_inode (data, grub_minix_le_to_cpu_ino (ino));
info.dir = ((GRUB_MINIX_INODE_MODE (data)
& GRUB_MINIX_IFDIR) == GRUB_MINIX_IFDIR);
if (hook (filename, &info) ? 1 : 0)
@@ -556,7 +636,9 @@
\f
static struct grub_fs grub_minix_fs =
{
-#ifdef MODE_MINIX2
+#if defined(MODE_MINIX3)
+ .name = "minix3",
+#elif defined(MODE_MINIX2)
.name = "minix2",
#else
.name = "minix",
@@ -568,7 +650,9 @@
.next = 0
};
-#ifdef MODE_MINIX2
+#if defined(MODE_MINIX3)
+GRUB_MOD_INIT(minix3)
+#elif defined(MODE_MINIX2)
GRUB_MOD_INIT(minix2)
#else
GRUB_MOD_INIT(minix)
@@ -578,7 +662,9 @@
my_mod = mod;
}
-#ifdef MODE_MINIX2
+#if defined(MODE_MINIX3)
+GRUB_MOD_FINI(minix3)
+#elif defined(MODE_MINIX2)
GRUB_MOD_FINI(minix2)
#else
GRUB_MOD_FINI(minix)
=== added file 'grub-core/fs/minix3.c'
--- grub-core/fs/minix3.c 1970-01-01 00:00:00 +0000
+++ grub-core/fs/minix3.c 2011-04-10 15:36:48 +0000
@@ -0,0 +1,2 @@
+#define MODE_MINIX3 1
+#include "minix.c"
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
^ permalink raw reply
* Re: [Qemu-devel] tcg/tcg.c:1892: tcg fatal error
From: Artyom Tarasenko @ 2011-04-10 18:35 UTC (permalink / raw)
To: Blue Swirl; +Cc: peter.maydell, qemu-devel, Aurelien Jarno
In-Reply-To: <BANLkTikeAmZ9M-ey_G4E7yWjbzOs-DB2Ww@mail.gmail.com>
On Sun, Apr 10, 2011 at 7:57 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Sun, Apr 10, 2011 at 8:48 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
>> On Sun, Apr 10, 2011 at 4:44 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
>>> On Sun, Apr 10, 2011 at 5:09 PM, Artyom Tarasenko <atar4qemu@gmail.com> wrote:
>>>> On Sun, Apr 10, 2011 at 3:24 PM, Aurelien Jarno <aurelien@aurel32.net> wrote:
>>>>> On Sun, Apr 10, 2011 at 02:29:59PM +0200, Artyom Tarasenko wrote:
>>>>>> Trying to boot some proprietary OS I get qemu-system-sparc64 crash with a
>>>>>>
>>>>>> tcg/tcg.c:1892: tcg fatal error
>>>>>>
>>>>>> error message.
>>>>>>
>>>>>> It looks like it can be a platform independent bug though, because
>>>>>> when a '-singlestep' option IS present, qemu doesn't crash and seems
>>>>>> to translate the code properly.
>>>>>>
>>>>>> (gdb) bt
>>>>>> #0 0x00000032c2e327f5 in raise () from /lib64/libc.so.6
>>>>>> #1 0x00000032c2e33fd5 in abort () from /lib64/libc.so.6
>>>>>> #2 0x000000000051933d in tcg_reg_alloc_call (s=<value optimized out>,
>>>>>> def=0x89d340, opc=INDEX_op_call, args=0x10acc98, dead_iargs=3) at
>>>>>> qemu/tcg/tcg.c:1892
>>>>>> #3 0x000000000051a557 in tcg_gen_code_common (s=0x10b8940,
>>>>>> gen_code_buf=0x40338b60 "I\213n@H\213] 3\355I\211\256\220") at
>>>>>> qemu/tcg/tcg.c:2099
>>>>>> #4 tcg_gen_code (s=0x10b8940, gen_code_buf=0x40338b60 "I\213n@H\213]
>>>>>> 3\355I\211\256\220") at qemu/tcg/tcg.c:2142
>>>>>> #5 0x00000000004d38f1 in cpu_sparc_gen_code (env=0x10cce10,
>>>>>> tb=0x7fffe91bc218, gen_code_size_ptr=0x7fffffffd9b4) at
>>>>>> qemu/translate-all.c:93
>>>>>> #6 0x00000000004d1fd7 in tb_gen_code (env=0x10cce10, pc=18868776,
>>>>>> cs_base=18868780, flags=15, cflags=0) at qemu/exec.c:989
>>>>>> #7 0x00000000004d4029 in tb_find_slow (env1=<value optimized out>) at
>>>>>> qemu/cpu-exec.c:167
>>>>>> #8 tb_find_fast (env1=<value optimized out>) at cpu-exec.c:194
>>>>>> #9 cpu_sparc_exec (env1=<value optimized out>) at qemu/cpu-exec.c:556
>>>>>> #10 0x0000000000408868 in tcg_cpu_exec () at qemu/cpus.c:1066
>>>>>> #11 cpu_exec_all () at qemu/cpus.c:1102
>>>>>> #12 0x000000000053c756 in main_loop (argc=<value optimized out>,
>>>>>> argv=<value optimized out>, envp=<value optimized out>) at
>>>>>> qemu/vl.c:1430
>>>>>>
>>>>>> I inspected ts->val_type causing the abort() case and it turned out to be 0.
>>>>>>
>>>>>> The last lines of qemu.log (without -singlestep)
>>>>>> IN:
>>>>>> 0x00000000011fe9f0: rdpr %pstate, %g1
>>>>>> 0x00000000011fe9f4: wrpr %g1, 2, %pstate
>>>>>> --------------
>>>>>> IN:
>>>>>> 0x00000000011fe9f8: ldub [ %o0 ], %o1
>>>>>> 0x00000000011fe9fc: mov %o1, %o2
>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>>
>>>>>> Search PC...
>>>>>> Search PC...
>>>>>> Search PC...
>>>>>> Search PC...
>>>>>> Search PC...
>>>>>> Search PC...
>>>>>> --------------
>>>>>> IN:
>>>>>> 0x00000000011fe9f8: ldub [ %o0 ], %o1
>>>>>> 0x00000000011fe9fc: mov %o1, %o2
>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>>
>>>>>> 110521: Data Access MMU Miss (v=0068) pc=00000000011fe9f8
>>>>>> npc=00000000011fe9fc SP=000000000180ae41
>>>>>> pc: 00000000011fe9f8 npc: 00000000011fe9fc
>>>>>>
>>>>>> IN:
>>>>>> 0x00000000011fea00: rdpr %tick, %o3
>>>>>> 0x00000000011fea04: cmp %o1, %o2
>>>>>> 0x00000000011fea08: be %icc, 0x11fea00
>>>>>> 0x00000000011fea0c: ldub [ %o0 ], %o2
>>>>>> --------------
>>>>>> IN:
>>>>>> 0x00000000011fea10: brz,pn %o2, 0x11fe9f8
>>>>>> 0x00000000011fea14: mov %o2, %o4
>>>>>> --------------
>>>>>> IN:
>>>>>> 0x00000000011fea18: rdpr %tick, %o5
>>>>>> 0x00000000011fea1c: cmp %o2, %o4
>>>>>> 0x00000000011fea20: be %icc, 0x11fea18
>>>>>> 0x00000000011fea24: ldub [ %o0 ], %o4
>>>>>> --------------
>>>>>> IN:
>>>>>> 0x00000000011fea28: brz,pn %o4, 0x11fe9f4
>>>>>> 0x00000000011fea2c: wrpr %g0, %g1, %pstate
>>>>>> <EOF>
>>>>>>
>>>>>> The crash is 100% reproducible and happens always on the same place,
>>>>>> so it's probably a pure TCG issue, not related on getting the
>>>>>> external/timer interrupts.
>>>>>>
>>>>>> Do you need any additional info?
>>>>>>
>>>>>
>>>>> What would be interesting would be to get the corresponding TCG code
>>>>> from qemu.log (-d op,op_opt).
>>>>
>>>>
>>>> OP:
>>>> ---- 0x11fea28
>>>> ld_i64 tmp6,regwptr,$0x20
>>>> movi_i64 cond,$0x0
>>>> movi_i64 tmp8,$0x0
>>>> brcond_i64 tmp6,tmp8,ne,$0x0
>>>> movi_i64 cond,$0x1
>>>> set_label $0x0
>>>>
>>>> ---- 0x11fea2c
>>>> movi_i64 tmp7,$0x0
>>>> xor_i64 tmp0,tmp7,g1
>>>> movi_i64 pc,$0x11fea2c
>>>> movi_i64 tmp8,$compute_psr
>>>> call tmp8,$0x0,$0
>>>> movi_i64 tmp8,$0x0
>>>> brcond_i64 cond,tmp8,eq,$0x1
>>>> movi_i64 npc,$0x11fe9f4
>>>> br $0x2
>>>> set_label $0x1
>>>> movi_i64 npc,$0x11fea30
>>>> set_label $0x2
>>>> movi_i64 tmp8,$wrpstate
>>>> call tmp8,$0x0,$0,tmp0
>>>> mov_i64 pc,npc
>>>> movi_i64 tmp8,$0x4
>>>> add_i64 npc,npc,tmp8
>>>> exit_tb $0x0
>>>>
>>>> OP after liveness analysis:
>>>> ---- 0x11fea28
>>>> ld_i64 tmp6,regwptr,$0x20
>>>> movi_i64 cond,$0x0
>>>> movi_i64 tmp8,$0x0
>>>> brcond_i64 tmp6,tmp8,ne,$0x0
>>>> movi_i64 cond,$0x1
>>>> set_label $0x0
>>>>
>>>> ---- 0x11fea2c
>>>> nopn $0x2,$0x2
>>>> nopn $0x3,$0x68,$0x3
>>>> movi_i64 pc,$0x11fea2c
>>>> movi_i64 tmp8,$compute_psr
>>>> call tmp8,$0x0,$0
>>>> movi_i64 tmp8,$0x0
>>>> brcond_i64 cond,tmp8,eq,$0x1
>>>> movi_i64 npc,$0x11fe9f4
>>>> br $0x2
>>>> set_label $0x1
>>>> movi_i64 npc,$0x11fea30
>>>> set_label $0x2
>>>> movi_i64 tmp8,$wrpstate
>>>> call tmp8,$0x0,$0,tmp0
>>>> mov_i64 pc,npc
>>>> movi_i64 tmp8,$0x4
>>>> add_i64 npc,npc,tmp8
>>>> exit_tb $0x0
>>>> end
>>>>
>>>> Does it mean the last block is processed correctly and the crash
>>>> happens on the next instruction which doesn't make it to the log?
>>>> The next instruction would be a
>>>>
>>>> 0x00000000011fea30: retl
>>>>
>>>> Since it's a branch instruction I guess this would also be a tcg block boundary.
>>>
>>> Because abort() was called from tcg_reg_alloc_call, I'd say 'retl'
>>> (synthetic op for 'jmpl %o8 + 8, %g0') was the problem.
>>
>> Any idea why? retl is not a rare instruction...
>
> Sorry, calls are generated for helpers, so it's not 'jmpl' but the
> call to wrpstate helper.
And why it doesn't happen in a singlestep mode?
I tried to comment out
cpu_check_irqs(env);
in the helper_wrpstate but it made no difference. The only suspicious
thing left is register bank switching. Is it safe to switch register
banks in the helper function? Shouldn't we end the translation block
before?
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
^ permalink raw reply
* Re: [Qemu-devel] Re: [PATCH] hw/pflash_cfi02: Fix lazy reset of ROMD mode
From: Jordan Justen @ 2011-04-10 18:29 UTC (permalink / raw)
To: Jan Kiszka; +Cc: qemu-devel
In-Reply-To: <4DA16C6A.7090303@web.de>
On Sun, Apr 10, 2011 at 01:38, Jan Kiszka <jan.kiszka@web.de> wrote:
> Indeed, that block looks weird to its author today as well. But
> inverting the logic completely defeats the purpose of lazy mode
> switching (will likely file a patch to remove the block).
Looking at the 2nd parameter to the call, and the
pflash_register_memory code, it seems it only makes sense with the
!pfl->rom_mode.
I thought that the goal was to allow multiple write operations before
exiting to rom mode, but that a read will return it to rom mode. In
that case, this change seemed to fix it.
> We should
> instead switch back using the timer.
>
> So the question is: Did you actually see a problem that the flash was
> stuck in write mode, or did you just stumble over this strange code? In
> the former case, please explain the sequence or provide a trace.
I had enabled the debug trace messages and was probing the flash from
the efi shell on x86-64. I found that I would always see the debug
messages for reads, after I started writing to the flash.
This change allowed the flash to go back to a rom mode where the debug
prints would then disappear for subsequent reads.
-Jordan
^ permalink raw reply
* [Qemu-devel] [PATCH 3/4] qemu-timer: Avoid type casts
From: Stefan Weil @ 2011-04-10 18:28 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Paolo Bonzini, QEMU Developers
In-Reply-To: <1302460123-25704-1-git-send-email-weil@mail.berlios.de>
The type casts are no longer needed after some small changes
in struct qemu_alarm_timer. This also improves readability
of the code.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
qemu-timer.c | 42 ++++++++++++++++++++++--------------------
1 files changed, 22 insertions(+), 20 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index c3ad72a..26e5ea3 100644
--- a/qemu-timer.c
+++ b/qemu-timer.c
@@ -169,8 +169,12 @@ struct qemu_alarm_timer {
int (*start)(struct qemu_alarm_timer *t);
void (*stop)(struct qemu_alarm_timer *t);
void (*rearm)(struct qemu_alarm_timer *t);
- void *priv;
-
+#if defined(__linux__)
+ int fd;
+ timer_t timer;
+#elif defined(_WIN32)
+ HANDLE timer;
+#endif
char expired;
char pending;
};
@@ -289,18 +293,16 @@ static struct qemu_alarm_timer alarm_timers[] = {
#ifndef _WIN32
#ifdef __linux__
{"dynticks", dynticks_start_timer,
- dynticks_stop_timer, dynticks_rearm_timer, NULL},
+ dynticks_stop_timer, dynticks_rearm_timer},
/* HPET - if available - is preferred */
- {"hpet", hpet_start_timer, hpet_stop_timer, NULL, NULL},
+ {"hpet", hpet_start_timer, hpet_stop_timer, NULL},
/* ...otherwise try RTC */
- {"rtc", rtc_start_timer, rtc_stop_timer, NULL, NULL},
+ {"rtc", rtc_start_timer, rtc_stop_timer, NULL},
#endif
- {"unix", unix_start_timer, unix_stop_timer, NULL, NULL},
+ {"unix", unix_start_timer, unix_stop_timer, NULL},
#else
- {"dynticks", win32_start_timer,
- win32_stop_timer, win32_rearm_timer, NULL},
- {"win32", win32_start_timer,
- win32_stop_timer, NULL, NULL},
+ {"dynticks", win32_start_timer, win32_stop_timer, win32_rearm_timer},
+ {"win32", win32_start_timer, win32_stop_timer, NULL},
#endif
{NULL, }
};
@@ -773,7 +775,7 @@ static int hpet_start_timer(struct qemu_alarm_timer *t)
goto fail;
enable_sigio_timer(fd);
- t->priv = (void *)(long)fd;
+ t->fd = fd;
return 0;
fail:
@@ -783,7 +785,7 @@ fail:
static void hpet_stop_timer(struct qemu_alarm_timer *t)
{
- int fd = (long)t->priv;
+ int fd = t->fd;
close(fd);
}
@@ -812,14 +814,14 @@ static int rtc_start_timer(struct qemu_alarm_timer *t)
enable_sigio_timer(rtc_fd);
- t->priv = (void *)(long)rtc_fd;
+ t->fd = rtc_fd;
return 0;
}
static void rtc_stop_timer(struct qemu_alarm_timer *t)
{
- int rtc_fd = (long)t->priv;
+ int rtc_fd = t->fd;
close(rtc_fd);
}
@@ -854,21 +856,21 @@ static int dynticks_start_timer(struct qemu_alarm_timer *t)
return -1;
}
- t->priv = (void *)(long)host_timer;
+ t->timer = host_timer;
return 0;
}
static void dynticks_stop_timer(struct qemu_alarm_timer *t)
{
- timer_t host_timer = (timer_t)(long)t->priv;
+ timer_t host_timer = t->timer;
timer_delete(host_timer);
}
static void dynticks_rearm_timer(struct qemu_alarm_timer *t)
{
- timer_t host_timer = (timer_t)(long)t->priv;
+ timer_t host_timer = t->timer;
struct itimerspec timeout;
int64_t nearest_delta_ns = INT64_MAX;
int64_t current_ns;
@@ -970,13 +972,13 @@ static int win32_start_timer(struct qemu_alarm_timer *t)
return -1;
}
- t->priv = (PVOID) hTimer;
+ t->timer = hTimer;
return 0;
}
static void win32_stop_timer(struct qemu_alarm_timer *t)
{
- HANDLE hTimer = t->priv;
+ HANDLE hTimer = t->timer;
if (hTimer) {
DeleteTimerQueueTimer(NULL, hTimer, NULL);
@@ -985,7 +987,7 @@ static void win32_stop_timer(struct qemu_alarm_timer *t)
static void win32_rearm_timer(struct qemu_alarm_timer *t)
{
- HANDLE hTimer = t->priv;
+ HANDLE hTimer = t->timer;
int nearest_delta_ms;
BOOLEAN success;
--
1.7.2.5
^ permalink raw reply related
* [Qemu-devel] [PATCH 2/4] qemu-timer: Remove unneeded include statement (w32)
From: Stefan Weil @ 2011-04-10 18:28 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Paolo Bonzini, QEMU Developers
In-Reply-To: <1302460123-25704-1-git-send-email-weil@mail.berlios.de>
mmsystem.h is not needed in qemu-timer.h, so remove it.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
qemu-timer.h | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/qemu-timer.h b/qemu-timer.h
index 75d5675..a932b09 100644
--- a/qemu-timer.h
+++ b/qemu-timer.h
@@ -7,7 +7,6 @@
#ifdef _WIN32
#include <windows.h>
-#include <mmsystem.h>
#endif
/* timers */
--
1.7.2.5
^ permalink raw reply related
* [Qemu-devel] [PATCH 4/4] qemu-timer: Fix timers for w32
From: Stefan Weil @ 2011-04-10 18:28 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Paolo Bonzini, QEMU Developers
In-Reply-To: <1302460123-25704-1-git-send-email-weil@mail.berlios.de>
Commit 68c23e5520e8286d79d96ab47c0ea722ceb75041 removed the
multimedia timer, but this timer is needed for certain
Linux kernels. Otherwise Linux boot stops with this error:
MP-BIOS bug: 8254 timer not connected to IO-APIC
So the multimedia timer is added again here.
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
qemu-timer.c | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 96 insertions(+), 0 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index 26e5ea3..a57197b 100644
--- a/qemu-timer.c
+++ b/qemu-timer.c
@@ -209,6 +209,10 @@ static void qemu_rearm_alarm_timer(struct qemu_alarm_timer *t)
#ifdef _WIN32
+static int mm_start_timer(struct qemu_alarm_timer *t);
+static void mm_stop_timer(struct qemu_alarm_timer *t);
+static void mm_rearm_timer(struct qemu_alarm_timer *t);
+
static int win32_start_timer(struct qemu_alarm_timer *t);
static void win32_stop_timer(struct qemu_alarm_timer *t);
static void win32_rearm_timer(struct qemu_alarm_timer *t);
@@ -301,6 +305,8 @@ static struct qemu_alarm_timer alarm_timers[] = {
#endif
{"unix", unix_start_timer, unix_stop_timer, NULL},
#else
+ {"mmtimer", mm_start_timer, mm_stop_timer, NULL},
+ {"mmtimer2", mm_start_timer, mm_stop_timer, mm_rearm_timer},
{"dynticks", win32_start_timer, win32_stop_timer, win32_rearm_timer},
{"win32", win32_start_timer, win32_stop_timer, NULL},
#endif
@@ -949,6 +955,96 @@ static void unix_stop_timer(struct qemu_alarm_timer *t)
#ifdef _WIN32
+static MMRESULT mm_timer;
+static unsigned mm_period;
+
+static void CALLBACK mm_alarm_handler(UINT uTimerID, UINT uMsg,
+ DWORD_PTR dwUser, DWORD_PTR dw1,
+ DWORD_PTR dw2)
+{
+ struct qemu_alarm_timer *t = alarm_timer;
+ if (!t) {
+ return;
+ }
+ if (alarm_has_dynticks(t) || qemu_next_alarm_deadline() <= 0) {
+ t->expired = alarm_has_dynticks(t);
+ t->pending = 1;
+ qemu_notify_event();
+ }
+}
+
+static int mm_start_timer(struct qemu_alarm_timer *t)
+{
+ TIMECAPS tc;
+ UINT flags;
+
+ memset(&tc, 0, sizeof(tc));
+ timeGetDevCaps(&tc, sizeof(tc));
+
+ mm_period = tc.wPeriodMin;
+ timeBeginPeriod(mm_period);
+
+ flags = TIME_CALLBACK_FUNCTION;
+ if (alarm_has_dynticks(t)) {
+ flags |= TIME_ONESHOT;
+ } else {
+ flags |= TIME_PERIODIC;
+ }
+
+ mm_timer = timeSetEvent(1, /* interval (ms) */
+ mm_period, /* resolution */
+ mm_alarm_handler, /* function */
+ (DWORD)t, /* parameter */
+ flags);
+
+ if (!mm_timer) {
+ fprintf(stderr, "Failed to initialize win32 alarm timer: %ld\n",
+ GetLastError());
+ timeEndPeriod(mm_period);
+ return -1;
+ }
+
+ return 0;
+}
+
+static void mm_stop_timer(struct qemu_alarm_timer *t)
+{
+ timeKillEvent(mm_timer);
+ timeEndPeriod(mm_period);
+}
+
+static void mm_rearm_timer(struct qemu_alarm_timer *t)
+{
+ int nearest_delta_ms;
+
+ assert(alarm_has_dynticks(t));
+ if (!active_timers[QEMU_CLOCK_REALTIME] &&
+ !active_timers[QEMU_CLOCK_VIRTUAL] &&
+ !active_timers[QEMU_CLOCK_HOST]) {
+ return;
+ }
+
+ timeKillEvent(mm_timer);
+
+ nearest_delta_ms = (qemu_next_alarm_deadline() + 999999) / 1000000;
+ if (nearest_delta_ms < 1) {
+ nearest_delta_ms = 1;
+ }
+ mm_timer = timeSetEvent(nearest_delta_ms,
+ mm_period,
+ mm_alarm_handler,
+ (DWORD)t,
+ TIME_ONESHOT | TIME_CALLBACK_FUNCTION);
+
+ if (!mm_timer) {
+ fprintf(stderr, "Failed to re-arm win32 alarm timer %ld\n",
+ GetLastError());
+
+ timeEndPeriod(mm_period);
+ exit(1);
+ }
+}
+
static int win32_start_timer(struct qemu_alarm_timer *t)
{
HANDLE hTimer;
--
1.7.2.5
^ permalink raw reply related
* [Qemu-devel] [PATCH 1/4] qemu-timer: Add and use new function qemu_timer_expired_ns
From: Stefan Weil @ 2011-04-10 18:28 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Paolo Bonzini, QEMU Developers
In-Reply-To: <1302460123-25704-1-git-send-email-weil@mail.berlios.de>
This simply moves code which is used three times
into a new function thus improving readability.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
qemu-timer.c | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/qemu-timer.c b/qemu-timer.c
index 50f1943..c3ad72a 100644
--- a/qemu-timer.c
+++ b/qemu-timer.c
@@ -177,6 +177,11 @@ struct qemu_alarm_timer {
static struct qemu_alarm_timer *alarm_timer;
+static bool qemu_timer_expired_ns(QEMUTimer *timer_head, int64_t current_time)
+{
+ return timer_head && (timer_head->expire_time <= current_time);
+}
+
int qemu_alarm_pending(void)
{
return alarm_timer->pending;
@@ -438,10 +443,9 @@ static void qemu_mod_timer_ns(QEMUTimer *ts, int64_t expire_time)
pt = &active_timers[ts->clock->type];
for(;;) {
t = *pt;
- if (!t)
- break;
- if (t->expire_time > expire_time)
+ if (!qemu_timer_expired_ns(t, expire_time)) {
break;
+ }
pt = &t->next;
}
ts->expire_time = expire_time;
@@ -478,9 +482,7 @@ int qemu_timer_pending(QEMUTimer *ts)
int qemu_timer_expired(QEMUTimer *timer_head, int64_t current_time)
{
- if (!timer_head)
- return 0;
- return (timer_head->expire_time <= current_time * timer_head->scale);
+ return qemu_timer_expired_ns(timer_head, current_time * timer_head->scale);
}
static void qemu_run_timers(QEMUClock *clock)
@@ -495,8 +497,9 @@ static void qemu_run_timers(QEMUClock *clock)
ptimer_head = &active_timers[clock->type];
for(;;) {
ts = *ptimer_head;
- if (!ts || ts->expire_time > current_time)
+ if (!qemu_timer_expired_ns(ts, current_time)) {
break;
+ }
/* remove timer from the list before calling the callback */
*ptimer_head = ts->next;
ts->next = NULL;
--
1.7.2.5
^ permalink raw reply related
* Re: linux-next: manual merge of the sound tree with Linus' tree
From: Mark Brown @ 2011-04-10 18:29 UTC (permalink / raw)
To: Takashi Iwai; +Cc: Stephen Rothwell, linux-next, linux-kernel, Lucas De Marchi
In-Reply-To: <s5hoc4ee88p.wl%tiwai@suse.de>
On Sun, Apr 10, 2011 at 12:00:38PM +0200, Takashi Iwai wrote:
> It'd be helpful if you can resolve in your tree.
I'll do so whenever the next -rc comes out - I know Linus isn't fond of
people pulling random untagged commits.
> I've been sick and can't work much since days ago.
Oh dear, get well soon :(
^ permalink raw reply
* [Qemu-devel] qemu-timer: Clean code and re-add multimedia timers for windows
From: Stefan Weil @ 2011-04-10 18:28 UTC (permalink / raw)
To: Anthony Liguori; +Cc: Paolo Bonzini, QEMU Developers
This patch series contains patches for qemu-timer.
The first 3 patches try to improve readability of the code.
Patch 1 was already sent to qemu-devel.
The last patch fixes a problem reported by a user of my QEMU for Windows
binaries: the multimedia timers are needed when users want to run current
Linux distributions. Instead of reverting the patch which removed these
timers, I re-add them here (so we have 4 timers for windows now) and
cleaned the original code a little bit.
[PATCH 1/4] qemu-timer: Add and use new function qemu_timer_expired_ns
[PATCH 2/4] qemu-timer: Remove unneeded include statement (w32)
[PATCH 3/4] qemu-timer: Avoid type casts
[PATCH 4/4] qemu-timer: Fix timers for w32
^ permalink raw reply
* Re: Firmware files for Ralink RT28x0
From: Larry Finger @ 2011-04-10 18:26 UTC (permalink / raw)
To: Ivo Van Doorn; +Cc: Xose Vazquez Perez, linux-wireless, users
In-Reply-To: <BANLkTimp6h9x0JC0HzSpKzdbKLOw=ioUvw@mail.gmail.com>
On 04/10/2011 12:35 PM, Ivo Van Doorn wrote:
> Hi.
>
>>> I notice that rt2800{pci,usb} each specify only one firmware image,
>>> regardless of the controller version.
>>>
>>> This is inconsistent with rt28{6,7}0sta and with the firmware images in
>>> linux-firmware.
>>>
>>> If you think that a single image per bus type can cover all controllers,
>>> please identify those firmware images, test them on each hardware
>>> generation, and get them into linux-firmware.
>>
>> querida:/datos/kernel/linux-2.6/drivers/net/wireless/rt2x00 $ grep "\.bin" *
>> rt2800pci.h:#define FIRMWARE_RT2860 "rt2860.bin"
>> rt2800usb.h:#define FIRMWARE_RT2870 "rt2870.bin"
>> rt61pci.h:#define FIRMWARE_RT2561 "rt2561.bin"
>> rt61pci.h:#define FIRMWARE_RT2561s "rt2561s.bin"
>> rt61pci.h:#define FIRMWARE_RT2661 "rt2661.bin"
>> rt73usb.h:#define FIRMWARE_RT2571 "rt73.bin"
>>
>> rt3070.bin rt3071.bin rt3090.bin should be deleted from linux-firmware.
>> They were only need by staging drivers.
>
> True, but the rt2860 and rt2870 firmware file are outdated in the
> linux-firmware,
> and probably don't support the rt3090 or other more recent chipsets. So before
> they can be removed, those files must be updated.
As I wrote earlier, my RT3090 is supported by rt2860.bin. I haven't tested
everything, but is functioned in STA and ad-hoc modes.
Larry
^ permalink raw reply
* Re: [PATCH 3/3] recipes, classes: import a lot of recipes from meta-shr
From: Martin Jansa @ 2011-04-10 18:22 UTC (permalink / raw)
To: openembedded-devel
In-Reply-To: <20110410150900.GA13532@sakrah.homelinux.org>
[-- Attachment #1: Type: text/plain, Size: 36863 bytes --]
On Sun, Apr 10, 2011 at 08:09:00AM -0700, Khem Raj wrote:
> On (10/04/11 14:42), Martin Jansa wrote:
> > * tested on shr-lite-image for om-gta02 and nokia900 (with meta-shr layer)
> > ---
> > meta-oe/classes/gitpkgv.bbclass | 84 +
> > meta-oe/classes/gitver.bbclass | 80 +
> > meta-oe/classes/glx-use-tls.bbclass | 7 +
> > meta-oe/classes/gpe.bbclass | 17 +
> > meta-oe/classes/srctree.bbclass | 123 +
> > meta-oe/recipes-connectivity/bluez/bluez4.inc | 71 +
> > .../bluez/bluez4/bluetooth.conf | 16 +
>
> can we call is bluez as we may not import bluez 3.x
If we all agree, then I'm fine with it. Some people wanted for OE
to split bluez-libs-4 and bluez-utils-4 like bluez-3 was.
So maybe someone else could work on it from here (as I'm not interested
in splitted recipes when building full (with X11/gstreamer) images
usually.
> > .../fix-dfutool-usb-declaration-mismatch.patch | 13 +
> > .../bluez/bluez4/hid2hci_usb_init.patch | 33 +
> > .../bluez/bluez4/sbc-thumb.patch | 11 +
> > meta-oe/recipes-connectivity/bluez/bluez4_4.91.bb | 15 +
> > meta-oe/recipes-connectivity/connman/connman.inc | 79 +
> > .../recipes-connectivity/connman/connman/connman | 42 +
> > .../connman/connman/link-against-libnl2.patch | 13 +
> > .../connman/connman/shr/connman | 42 +
> > .../recipes-connectivity/connman/connman_0.72.bb | 31 +
> > .../phonet-utils/phonet-utils_git.bb | 18 +
> > meta-oe/recipes-core/meta/distro-feed-configs.bb | 32 +
> > meta-oe/recipes-core/tasks/task-cli-tools.bb | 52 +
> > meta-oe/recipes-core/tasks/task-x11.bb | 43 +
> > .../gdbus-binding-tool/gdbus-binding-tool/COPYING | 482 +
> > .../gdbus-binding-tool/gdbus-binding-tool_git.bb | 37 +
> > .../use-usr-bin-env-for-python.patch | 20 +
> > .../gobject-introspection_0.9.10.bb | 32 +
> > .../recipes-devtools/json-glib/json-glib_0.10.4.bb | 14 +
> > .../libcanberra-increase-buffer-size.patch | 13 +
> > .../libcanberra/libcanberra_0.26.bb | 56 +
> > meta-oe/recipes-devtools/libgee/libgee.inc | 18 +
> > meta-oe/recipes-devtools/libgee/libgee_0.6.0.bb | 12 +
> > .../python/python-dateutil_1.4.1.bb | 24 +
> > .../python/python-numeric/no-lapack.patch | 33 +
> > .../recipes-devtools/python/python-numeric_24.2.bb | 15 +
> > .../recipes-devtools/python/python-pexpect_2.3.bb | 24 +
> > .../python/python-phoneutils_git.bb | 15 +
> > .../python/python-pyalsaaudio_0.4.bb | 16 +
> > .../recipes-devtools/python/python-pyserial_2.4.bb | 23 +
> > .../recipes-devtools/python/python-pyyaml/setup.py | 64 +
> > .../recipes-devtools/python/python-pyyaml_svn.bb | 22 +
> > .../python/python-vobject_0.8.1c.bb | 17 +
> > .../vala-dbus-binding-tool.inc | 16 +
> > .../vala-dbus-binding-tool_git.bb | 6 +
> > meta-oe/recipes-devtools/vala/vala.inc | 25 +
> > meta-oe/recipes-devtools/vala/vala_0.12.0.bb | 7 +
> > meta-oe/recipes-extended/tzcode/tzcode-native.inc | 18 +
> > .../recipes-extended/tzcode/tzcode-native_2011e.bb | 19 +
> > meta-oe/recipes-extended/tzdata/tzdata.inc | 178 +
> > meta-oe/recipes-extended/tzdata/tzdata_2011e.bb | 13 +
>
> can you propose the tzcode/tzdata updates to oe-core too ?
OK I'll send it in my next pull request to oe-core, but still waiting
for previous pull request to happen...
> > .../recipes-graphics/drm/libdrm-2.4.24/glamo.patch | 1095 ++
> > .../drm/libdrm-2.4.24/installtests.patch | 43 +
> > meta-oe/recipes-graphics/drm/libdrm_2.4.24.bb | 39 +
> > meta-oe/recipes-graphics/mesa/README | 12 +
> > meta-oe/recipes-graphics/mesa/mesa-7.10.2.inc | 19 +
> > .../recipes-graphics/mesa/mesa-7.10.2/glamo.patch | 2425 +++
> > .../recipes-graphics/mesa/mesa-7.10.2/uclibc.patch | 26 +
> > meta-oe/recipes-graphics/mesa/mesa-common.inc | 53 +
> > meta-oe/recipes-graphics/mesa/mesa-dri.inc | 10 +
> > meta-oe/recipes-graphics/mesa/mesa-dri_7.10.2.bb | 4 +
> > meta-oe/recipes-graphics/mesa/mesa-xlib.inc | 2 +
> > meta-oe/recipes-graphics/mesa/mesa-xlib_7.10.2.bb | 4 +
> > meta-oe/recipes-graphics/mesa/mesa_7.10.2.bb | 6 +
> > .../recipes-graphics/tasks/task-fonts-truetype.bb | 40 +
> > .../ttf-fonts/ttf-liberation_0.2.bb | 23 +
> > .../pointercal-xinput/iphone3g/pointercal.xinput | 1 +
> > .../pointercal-xinput/nokia900/pointercal.xinput | 2 +
> > .../pointercal-xinput/om-gta01/pointercal.xinput | 2 +
> > .../pointercal-xinput/om-gta02/pointercal.xinput | 2 +
> > .../pointercal-xinput/pointercal.xinput | 1 +
> > .../xinput-calibrator/pointercal-xinput_0.0.bb | 21 +
> > .../xinput-calibrator/xinput-calibrator.inc | 8 +
> > .../xinput-calibrator/xinput-calibrator_0.6.1.bb | 17 +
> > meta-oe/recipes-graphics/xorg-app/rgb_1.0.4.bb | 10 +
> > meta-oe/recipes-graphics/xorg-app/xinput_1.5.3.bb | 8 +
> > .../recipes-graphics/xorg-app/xorg-app-common.inc | 15 +
> > .../recipes-graphics/xorg-doc/xorg-doc-common.inc | 12 +
> > .../xorg-doc/xorg-sgml-doctools_1.7.bb | 8 +
> > .../xorg-driver/xf86-input-keyboard_1.6.0.bb | 17 +
> > .../xorg-driver/xf86-input-mouse_1.7.0.bb | 17 +
> > .../xf86-input-tslib/10-x11-input-tslib.fdi | 11 +
> > .../xf86-input-tslib/99-xf86-input-tslib.rules | 5 +
> > .../xf86-input-tslib/double-free-crash.patch | 20 +
> > .../xserver-174-XGetPointerControl.patch | 34 +
> > .../xorg-driver/xf86-input-tslib_0.0.6.bb | 32 +
> > .../xorg-driver/xf86-video-fbdev_0.4.2.bb | 9 +
> > ...efine-GLAMO_CMDQ_MAX_COUNT-instead-of-mag.patch | 66 +
> > .../xorg-driver/xf86-video-glamo_git.bb | 19 +
> > .../xorg-driver/xorg-driver-common.inc | 40 +
> > .../xorg-driver/xorg-driver-input.inc | 4 +
> > .../xorg-driver/xorg-driver-video.inc | 4 +
> > .../xorg-lib/liblbxutil-1.1.0/mkg3states-1.1.patch | 55 +
> > .../recipes-graphics/xorg-lib/liblbxutil_1.1.0.bb | 14 +
> > .../xorg-lib/libx11-1.4.1/keysymdef_include.patch | 19 +
> > .../libx11-1.4.1/x11_disable_makekeys.patch | 29 +
> > .../xorg-lib/libx11-1.4.3/keysymdef_include.patch | 19 +
> > .../libx11-1.4.3/x11_disable_makekeys.patch | 29 +
> > meta-oe/recipes-graphics/xorg-lib/libx11.inc | 52 +
> > meta-oe/recipes-graphics/xorg-lib/libx11_1.4.1.bb | 12 +
> > meta-oe/recipes-graphics/xorg-lib/libx11_1.4.3.bb | 12 +
> > meta-oe/recipes-graphics/xorg-lib/libxaw_1.0.9.bb | 28 +
> > meta-oe/recipes-graphics/xorg-lib/libxfixes_5.0.bb | 22 +
> > meta-oe/recipes-graphics/xorg-lib/libxi_1.4.2.bb | 21 +
> > .../recipes-graphics/xorg-lib/libxkbui_1.0.2.bb | 10 +
> > meta-oe/recipes-graphics/xorg-lib/libxt_1.1.1.bb | 37 +
> > meta-oe/recipes-graphics/xorg-lib/pixman_0.20.0.bb | 4 +-
> > meta-oe/recipes-graphics/xorg-lib/pixman_0.21.4.bb | 4 +-
> > .../recipes-graphics/xorg-lib/xorg-lib-common.inc | 3 +-
> > .../recipes-graphics/xorg-proto/fixesproto_5.0.bb | 21 +
> > .../recipes-graphics/xorg-proto/xextproto_7.2.0.bb | 19 +
> > .../xorg-proto/xorg-proto-common.inc | 4 +-
> > .../recipes-graphics/xorg-proto/xproto_7.0.21.bb | 16 +
> > .../xorg-util/util-macros_1.13.0.bb | 15 +
> > .../xorg-util/xorg-util-common.inc | 11 +
> > .../xorg-xserver/xorg-xserver-common.inc | 112 +
> > ...ack-assume-pixman-supports-overlapped-blt.patch | 14 +
> > .../hack-fbdev-ignore-return-mode.patch | 39 +
> > .../xorg-xserver/xserver-xorg-1.9.4/dolt-fix.patch | 22 +
> > ...ack-assume-pixman-supports-overlapped-blt.patch | 14 +
> > .../hack-fbdev-ignore-return-mode.patch | 39 +
> > .../xserver-xorg-1.9.4/randr-support.patch | 102 +
> > .../xserver-xorg-conf/am3517-evm/xorg.conf | 29 +
> > .../xserver-xorg-conf/am37x-evm/xorg.conf | 29 +
> > .../xserver-xorg-conf/archos5/xorg.conf | 29 +
> > .../xserver-xorg-conf/archos5it/xorg.conf | 29 +
> > .../xserver-xorg-conf/at91sam9263ek/xorg.conf | 11 +
> > .../xserver-xorg-conf/at91sam9g45ek/xorg.conf | 23 +
> > .../xserver-xorg-conf/babbage/xorg.conf | 56 +
> > .../xserver-xorg-conf/beagleboard/xorg.conf | 29 +
> > .../xorg-xserver/xserver-xorg-conf/bug/xorg.conf | 75 +
> > .../xorg-xserver/xserver-xorg-conf/bug20/xorg.conf | 37 +
> > .../xserver-xorg-conf/cm-t35/xorg.conf | 29 +
> > .../xserver-xorg-conf/dm37x-evm/xorg.conf | 29 +
> > .../xserver-xorg-conf/eee701/xorg.conf | 97 +
> > .../xserver-xorg-conf/htcdream/xorg.conf | 69 +
> > .../xserver-xorg-conf/htcleo/xorg.conf | 73 +
> > .../xserver-xorg-conf/igep0020/xorg.conf | 29 +
> > .../xorg-xserver/xserver-xorg-conf/ion/xorg.conf | 51 +
> > .../xserver-xorg-conf/iphone3g/xorg.conf | 29 +
> > .../xorg-xserver/xserver-xorg-conf/mh355/xorg.conf | 47 +
> > .../xserver-xorg-conf/nokia800/xorg.conf | 29 +
> > .../xserver-xorg-conf/nokia900/xorg.conf | 62 +
> > .../xserver-xorg-conf/om-gta01/xorg.conf | 49 +
> > .../xserver-xorg-conf/om-gta02/xorg.conf | 55 +
> > .../xserver-xorg-conf/omap3-pandora/xorg.conf | 24 +
> > .../xserver-xorg-conf/omap3-touchbook/xorg.conf | 25 +
> > .../xorg-xserver/xserver-xorg-conf/omap3/xorg.conf | 29 +
> > .../xserver-xorg-conf/omap3evm/xorg.conf | 29 +
> > .../xserver-xorg-conf/omapzoom/xorg.conf | 29 +
> > .../xserver-xorg-conf/omapzoom2/xorg.conf | 29 +
> > .../xserver-xorg-conf/omapzoom36x/xorg.conf | 29 +
> > .../xorg-xserver/xserver-xorg-conf/overo/xorg.conf | 29 +
> > .../xserver-xorg-conf/palmpre/xorg.conf | 58 +
> > .../xserver-xorg-conf/ronetix-pm9263/xorg.conf | 47 +
> > .../xorg-xserver/xserver-xorg-conf/spitz/xorg.conf | 49 +
> > .../xserver-xorg-conf/vortex86sx/xorg.conf | 13 +
> > .../xserver-xorg-conf/xilinx-ml507/xorg.conf | 39 +
> > .../xserver-xorg-conf/xilinx-virtex5/xorg.conf | 38 +
> > .../xorg-xserver/xserver-xorg-conf_0.1.bb | 17 +
> > .../xorg-xserver/xserver-xorg_1.10.0.901.bb | 29 +
> > .../xorg-xserver/xserver-xorg_1.9.4.bb | 31 +
> > .../xorg-xserver/xserver-xorg_git.bb | 38 +
> > .../89xTs_Calibrate.xinput_calibrator.patch | 12 +
> > .../xserver-common-1.34/89xdgautostart.sh | 9 +
> > .../xserver-common-1.34/90xXWindowManager.patch | 11 +
> > .../Xserver.add.dpi.for.gta.patch | 29 +
> > .../Xserver.add.nocursor.for.gta.patch | 20 +
> > .../Xserver.add.xserver-system.patch | 12 +
> > .../xserver-common-1.34/Xserver.n900.patch | 17 +
> > .../xserver-common-1.34/gplv2-license.patch | 353 +
> > .../xserver-common/xserver-common-1.34/setDPI.sh | 92 +
> > .../xserver-common/xserver-common_1.34.bb | 38 +
> > .../xserver-nodm-init-2.0/gplv2-license.patch | 353 +
> > .../xserver-nodm-init-2.0/xserver-nodm | 44 +
> > .../xserver-nodm-init/xserver-nodm-init_2.0.bb | 27 +
> > .../ca-certificates_20090814+nmu2.bb | 40 +
> > .../ca-certificates/files/remove-c-rehash.patch | 29 +
> > .../dfu-util/dfu-util-native_svn.bb | 16 +
> > meta-oe/recipes-support/dfu-util/dfu-util.inc | 13 +
> > meta-oe/recipes-support/dfu-util/dfu-util_0.1.bb | 7 +
> > meta-oe/recipes-support/dfu-util/dfu-util_svn.bb | 16 +
> > .../recipes-support/farsight/farsight2_0.0.22.bb | 23 +
> > meta-oe/recipes-support/farsight/libnice_0.0.13.bb | 25 +
> > .../recipes-support/fbset/fbset-2.1/makefile.patch | 11 +
> > meta-oe/recipes-support/fbset/fbset-modes.bb | 17 +
> > meta-oe/recipes-support/fbset/fbset-modes/fb.modes | 3 +
> > .../fbset/fbset-modes/om-gta01/fb.modes | 29 +
> > .../fbset/fbset-modes/omap3-pandora/fb.modes | 6 +
> > .../fbset/fbset-modes/qemuarm/fb.modes | 17 +
> > .../fbset/fbset-modes/qemumips/fb.modes | 17 +
> > meta-oe/recipes-support/fbset/fbset_2.1.bb | 38 +
> > meta-oe/recipes-support/lcms/lcms_1.17.bb | 14 +
> > .../libiconv/libiconv-1.13.1/autoconf.patch |16018 ++++++++++++++++++++
> > meta-oe/recipes-support/libiconv/libiconv.inc | 15 +
> > .../recipes-support/libiconv/libiconv_1.13.1.bb | 25 +
> > meta-oe/recipes-support/libnl/libnl.inc | 9 +
> > .../recipes-support/libnl/libnl/fix-pc-file.patch | 11 +
> > .../libnl/libnl/fix-pktloc-dep-race.patch | 20 +
> > meta-oe/recipes-support/libnl/libnl_2.0.bb | 23 +
> > meta-oe/recipes-support/libnl/libnl_git.bb | 20 +
> > .../libsdl-ttf/libsdl-ttf-2.0.10/configure.patch | 13 +
> > .../libsdl-ttf/libsdl-ttf_2.0.10.bb | 30 +
> > meta-oe/recipes-support/libyaml/libyaml_0.1.3.bb | 14 +
> > .../lzma/lzma-4.65/001-large_files.patch | 13 +
> > .../recipes-support/lzma/lzma-4.65/002-lzmp.patch | 1059 ++
> > .../lzma/lzma-4.65/003-compile_fixes.patch | 26 +
> > .../lzma/lzma-4.65/100-static_library.patch | 70 +
> > .../lzma/lzma-4.65/makefile-cleanup.patch | 18 +
> > meta-oe/recipes-support/lzma/lzma.inc | 36 +
> > meta-oe/recipes-support/lzma/lzma_4.65.bb | 5 +
> > .../mpfr/mpfr-3.0.0/long-long-thumb.patch | 11 +
> > meta-oe/recipes-support/mpfr/mpfr-3.0.0/p4.patch | 1752 +++
> > meta-oe/recipes-support/mpfr/mpfr_3.0.0.bb | 30 +
>
> mpfr-3.0.0 is also in oe-core so I wonder if it would be better
> to provide these updates to oe-core instead
the important change is long-long-thumb.patch, but thumb OVERRIDE is not
available in oe-core afaik, I have it in meta-shr from good old
meta-shr/conf/distro/include/arm-thumb.inc from OE, so I'm not sure if
such change would be allowed in oe-core, but I hope that those
sane-toolchain* and similar distro/include configs will be in meta-oe
later (and I could drop them from meta-shr).
> > .../nano/nano-2.2.5/ncursesw.includedir.patch | 12 +
> > meta-oe/recipes-support/nano/nano.inc | 19 +
> > meta-oe/recipes-support/nano/nano_2.2.5.bb | 8 +
> > meta-oe/recipes-support/pidgin/pidgin.inc | 88 +
> > .../pidgin/pidgin/pidgin-cross-python-265.patch | 16 +
> > .../pidgin/pidgin/pidgin.desktop-set-icon.patch | 11 +
> > .../pidgin/pidgin/purple-OE-branding-25.patch | 16 +
> > .../pidgin/pidgin/sanitize-configure.ac.patch | 33 +
> > meta-oe/recipes-support/pidgin/pidgin_2.7.9.bb | 22 +
> > .../recipes-support/poppler/poppler-data_0.4.0.bb | 24 +
> > meta-oe/recipes-support/poppler/poppler-fpu.inc | 6 +
> > meta-oe/recipes-support/poppler/poppler.inc | 25 +
> > meta-oe/recipes-support/poppler/poppler_0.12.3.bb | 10 +
> > .../samsung-soc-utils/s3c24xx-gpio_svn.bb | 19 +
> > .../samsung-soc-utils/s3c64xx-gpio_svn.bb | 19 +
> > .../samsung-soc-utils/sjf2410-linux-native_svn.bb | 34 +
> > meta-oe/recipes-support/talloc/talloc_2.0.1.bb | 27 +
> > meta-oe/recipes-support/tangogps/tangogps.inc | 15 +
> > .../recipes-support/tangogps/tangogps_0.99.4.bb | 4 +
> > meta-oe/recipes-support/usbpath/usbpath_svn.bb | 19 +
> > .../vala-terminal/vala-terminal_git.bb | 18 +
> > meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb | 20 +
> > 232 files changed, 29616 insertions(+), 7 deletions(-)
> > create mode 100644 meta-oe/classes/gitpkgv.bbclass
> > create mode 100644 meta-oe/classes/gitver.bbclass
> > create mode 100644 meta-oe/classes/glx-use-tls.bbclass
> > create mode 100644 meta-oe/classes/gpe.bbclass
> > create mode 100644 meta-oe/classes/srctree.bbclass
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4.inc
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4/bluetooth.conf
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4/fix-dfutool-usb-declaration-mismatch.patch
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4/hid2hci_usb_init.patch
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4/sbc-thumb.patch
> > create mode 100644 meta-oe/recipes-connectivity/bluez/bluez4_4.91.bb
> > create mode 100644 meta-oe/recipes-connectivity/connman/connman.inc
> > create mode 100755 meta-oe/recipes-connectivity/connman/connman/connman
> > create mode 100644 meta-oe/recipes-connectivity/connman/connman/link-against-libnl2.patch
> > create mode 100755 meta-oe/recipes-connectivity/connman/connman/shr/connman
> > create mode 100644 meta-oe/recipes-connectivity/connman/connman_0.72.bb
> > create mode 100644 meta-oe/recipes-connectivity/phonet-utils/phonet-utils_git.bb
> > create mode 100644 meta-oe/recipes-core/meta/distro-feed-configs.bb
> > create mode 100644 meta-oe/recipes-core/tasks/task-cli-tools.bb
> > create mode 100644 meta-oe/recipes-core/tasks/task-x11.bb
> > create mode 100644 meta-oe/recipes-devtools/gdbus-binding-tool/gdbus-binding-tool/COPYING
> > create mode 100644 meta-oe/recipes-devtools/gdbus-binding-tool/gdbus-binding-tool_git.bb
> > create mode 100644 meta-oe/recipes-devtools/gobject-introspection/gobject-introspection/use-usr-bin-env-for-python.patch
> > create mode 100644 meta-oe/recipes-devtools/gobject-introspection/gobject-introspection_0.9.10.bb
> > create mode 100644 meta-oe/recipes-devtools/json-glib/json-glib_0.10.4.bb
> > create mode 100644 meta-oe/recipes-devtools/libcanberra/libcanberra/libcanberra-increase-buffer-size.patch
> > create mode 100644 meta-oe/recipes-devtools/libcanberra/libcanberra_0.26.bb
> > create mode 100644 meta-oe/recipes-devtools/libgee/libgee.inc
> > create mode 100644 meta-oe/recipes-devtools/libgee/libgee_0.6.0.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-dateutil_1.4.1.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-numeric/no-lapack.patch
> > create mode 100644 meta-oe/recipes-devtools/python/python-numeric_24.2.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-pexpect_2.3.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-phoneutils_git.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-pyalsaaudio_0.4.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-pyserial_2.4.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-pyyaml/setup.py
> > create mode 100644 meta-oe/recipes-devtools/python/python-pyyaml_svn.bb
> > create mode 100644 meta-oe/recipes-devtools/python/python-vobject_0.8.1c.bb
> > create mode 100644 meta-oe/recipes-devtools/vala-dbus-binding-tool/vala-dbus-binding-tool.inc
> > create mode 100644 meta-oe/recipes-devtools/vala-dbus-binding-tool/vala-dbus-binding-tool_git.bb
> > create mode 100644 meta-oe/recipes-devtools/vala/vala.inc
> > create mode 100644 meta-oe/recipes-devtools/vala/vala_0.12.0.bb
> > create mode 100644 meta-oe/recipes-extended/tzcode/tzcode-native.inc
> > create mode 100644 meta-oe/recipes-extended/tzcode/tzcode-native_2011e.bb
> > create mode 100644 meta-oe/recipes-extended/tzdata/tzdata.inc
> > create mode 100644 meta-oe/recipes-extended/tzdata/tzdata_2011e.bb
> > create mode 100644 meta-oe/recipes-graphics/drm/libdrm-2.4.24/glamo.patch
> > create mode 100644 meta-oe/recipes-graphics/drm/libdrm-2.4.24/installtests.patch
> > create mode 100644 meta-oe/recipes-graphics/drm/libdrm_2.4.24.bb
> > create mode 100644 meta-oe/recipes-graphics/mesa/README
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-7.10.2.inc
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-7.10.2/glamo.patch
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-7.10.2/uclibc.patch
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-common.inc
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-dri.inc
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-dri_7.10.2.bb
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-xlib.inc
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> > create mode 100644 meta-oe/recipes-graphics/mesa/mesa_7.10.2.bb
> > create mode 100644 meta-oe/recipes-graphics/tasks/task-fonts-truetype.bb
> > create mode 100644 meta-oe/recipes-graphics/ttf-fonts/ttf-liberation_0.2.bb
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput/iphone3g/pointercal.xinput
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput/nokia900/pointercal.xinput
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput/om-gta01/pointercal.xinput
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput/om-gta02/pointercal.xinput
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput/pointercal.xinput
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/xinput-calibrator.inc
> > create mode 100644 meta-oe/recipes-graphics/xinput-calibrator/xinput-calibrator_0.6.1.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-app/rgb_1.0.4.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-app/xinput_1.5.3.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-app/xorg-app-common.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-doc/xorg-doc-common.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-doc/xorg-sgml-doctools_1.7.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-keyboard_1.6.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-mouse_1.7.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-tslib/10-x11-input-tslib.fdi
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-tslib/99-xf86-input-tslib.rules
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-tslib/double-free-crash.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-tslib/xserver-174-XGetPointerControl.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-input-tslib_0.0.6.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-video-fbdev_0.4.2.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-video-glamo/0001-glamo-drm-define-GLAMO_CMDQ_MAX_COUNT-instead-of-mag.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-video-glamo_git.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xorg-driver-common.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xorg-driver-input.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-driver/xorg-driver-video.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/liblbxutil-1.1.0/mkg3states-1.1.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/liblbxutil_1.1.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11-1.4.1/keysymdef_include.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11-1.4.1/x11_disable_makekeys.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11-1.4.3/keysymdef_include.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11-1.4.3/x11_disable_makekeys.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11_1.4.1.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libx11_1.4.3.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxaw_1.0.9.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxfixes_5.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxi_1.4.2.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxkbui_1.0.2.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxt_1.1.1.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-proto/fixesproto_5.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-proto/xextproto_7.2.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-proto/xproto_7.0.21.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-util/util-macros_1.13.0.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-util/xorg-util-common.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xorg-xserver-common.inc
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.10.0.901/hack-assume-pixman-supports-overlapped-blt.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.10.0.901/hack-fbdev-ignore-return-mode.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.9.4/dolt-fix.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.9.4/hack-assume-pixman-supports-overlapped-blt.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.9.4/hack-fbdev-ignore-return-mode.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-1.9.4/randr-support.patch
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/am3517-evm/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/am37x-evm/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/archos5/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/archos5it/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/at91sam9263ek/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/at91sam9g45ek/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/babbage/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/beagleboard/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/bug/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/bug20/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/cm-t35/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/dm37x-evm/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/eee701/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/htcdream/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/htcleo/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/igep0020/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/ion/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/iphone3g/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/mh355/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/nokia800/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/nokia900/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/om-gta01/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/om-gta02/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omap3-pandora/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omap3-touchbook/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omap3/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omap3evm/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omapzoom/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omapzoom2/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/omapzoom36x/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/overo/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/palmpre/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/ronetix-pm9263/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/spitz/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/vortex86sx/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/xilinx-ml507/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/xilinx-virtex5/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf/xorg.conf
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg-conf_0.1.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg_1.10.0.901.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg_1.9.4.bb
> > create mode 100644 meta-oe/recipes-graphics/xorg-xserver/xserver-xorg_git.bb
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/89xTs_Calibrate.xinput_calibrator.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/89xdgautostart.sh
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/90xXWindowManager.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/Xserver.add.dpi.for.gta.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/Xserver.add.nocursor.for.gta.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/Xserver.add.xserver-system.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/Xserver.n900.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/gplv2-license.patch
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common-1.34/setDPI.sh
> > create mode 100644 meta-oe/recipes-graphics/xserver-common/xserver-common_1.34.bb
> > create mode 100644 meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init-2.0/gplv2-license.patch
> > create mode 100755 meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init-2.0/xserver-nodm
> > create mode 100644 meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb
> > create mode 100644 meta-oe/recipes-support/ca-certificates/ca-certificates_20090814+nmu2.bb
> > create mode 100644 meta-oe/recipes-support/ca-certificates/files/remove-c-rehash.patch
> > create mode 100644 meta-oe/recipes-support/dfu-util/dfu-util-native_svn.bb
> > create mode 100644 meta-oe/recipes-support/dfu-util/dfu-util.inc
> > create mode 100644 meta-oe/recipes-support/dfu-util/dfu-util_0.1.bb
> > create mode 100644 meta-oe/recipes-support/dfu-util/dfu-util_svn.bb
> > create mode 100644 meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
> > create mode 100644 meta-oe/recipes-support/farsight/libnice_0.0.13.bb
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-2.1/makefile.patch
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes.bb
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes/fb.modes
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes/om-gta01/fb.modes
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes/omap3-pandora/fb.modes
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes/qemuarm/fb.modes
> > create mode 100644 meta-oe/recipes-support/fbset/fbset-modes/qemumips/fb.modes
> > create mode 100644 meta-oe/recipes-support/fbset/fbset_2.1.bb
> > create mode 100644 meta-oe/recipes-support/lcms/lcms_1.17.bb
> > create mode 100644 meta-oe/recipes-support/libiconv/libiconv-1.13.1/autoconf.patch
> > create mode 100644 meta-oe/recipes-support/libiconv/libiconv.inc
> > create mode 100644 meta-oe/recipes-support/libiconv/libiconv_1.13.1.bb
> > create mode 100644 meta-oe/recipes-support/libnl/libnl.inc
> > create mode 100644 meta-oe/recipes-support/libnl/libnl/fix-pc-file.patch
> > create mode 100644 meta-oe/recipes-support/libnl/libnl/fix-pktloc-dep-race.patch
> > create mode 100644 meta-oe/recipes-support/libnl/libnl_2.0.bb
> > create mode 100644 meta-oe/recipes-support/libnl/libnl_git.bb
> > create mode 100644 meta-oe/recipes-support/libsdl-ttf/libsdl-ttf-2.0.10/configure.patch
> > create mode 100644 meta-oe/recipes-support/libsdl-ttf/libsdl-ttf_2.0.10.bb
> > create mode 100644 meta-oe/recipes-support/libyaml/libyaml_0.1.3.bb
> > create mode 100644 meta-oe/recipes-support/lzma/lzma-4.65/001-large_files.patch
> > create mode 100644 meta-oe/recipes-support/lzma/lzma-4.65/002-lzmp.patch
> > create mode 100644 meta-oe/recipes-support/lzma/lzma-4.65/003-compile_fixes.patch
> > create mode 100644 meta-oe/recipes-support/lzma/lzma-4.65/100-static_library.patch
> > create mode 100644 meta-oe/recipes-support/lzma/lzma-4.65/makefile-cleanup.patch
> > create mode 100644 meta-oe/recipes-support/lzma/lzma.inc
> > create mode 100644 meta-oe/recipes-support/lzma/lzma_4.65.bb
> > create mode 100644 meta-oe/recipes-support/mpfr/mpfr-3.0.0/long-long-thumb.patch
> > create mode 100644 meta-oe/recipes-support/mpfr/mpfr-3.0.0/p4.patch
> > create mode 100644 meta-oe/recipes-support/mpfr/mpfr_3.0.0.bb
> > create mode 100644 meta-oe/recipes-support/nano/nano-2.2.5/ncursesw.includedir.patch
> > create mode 100644 meta-oe/recipes-support/nano/nano.inc
> > create mode 100644 meta-oe/recipes-support/nano/nano_2.2.5.bb
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin.inc
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin/pidgin-cross-python-265.patch
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin/pidgin.desktop-set-icon.patch
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin/purple-OE-branding-25.patch
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin/sanitize-configure.ac.patch
> > create mode 100644 meta-oe/recipes-support/pidgin/pidgin_2.7.9.bb
> > create mode 100644 meta-oe/recipes-support/poppler/poppler-data_0.4.0.bb
> > create mode 100644 meta-oe/recipes-support/poppler/poppler-fpu.inc
> > create mode 100644 meta-oe/recipes-support/poppler/poppler.inc
> > create mode 100644 meta-oe/recipes-support/poppler/poppler_0.12.3.bb
> > create mode 100644 meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb
> > create mode 100644 meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb
> > create mode 100644 meta-oe/recipes-support/samsung-soc-utils/sjf2410-linux-native_svn.bb
> > create mode 100644 meta-oe/recipes-support/talloc/talloc_2.0.1.bb
> > create mode 100644 meta-oe/recipes-support/tangogps/tangogps.inc
> > create mode 100644 meta-oe/recipes-support/tangogps/tangogps_0.99.4.bb
> > create mode 100644 meta-oe/recipes-support/usbpath/usbpath_svn.bb
> > create mode 100644 meta-oe/recipes-support/vala-terminal/vala-terminal_git.bb
> > create mode 100644 meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb
> >
>
> have you tried to boot some qemu targets ? with this changeset
no, only om-gta02 and nokia900..
thanks for review
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply
* Re: update fi-dna initial tuning file
From: Christoph Pfister @ 2011-04-10 18:24 UTC (permalink / raw)
To: Antti Palosaari; +Cc: linux-media@vger.kernel.org
In-Reply-To: <4D9F6341.9020107@iki.fi>
2011/4/8 Antti Palosaari <crope@iki.fi>:
> Moikka Christoph,
>
> Merge attached patch.
Updated, thanks.
> Antti
> --
> http://palosaari.fi/
Christoph
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.