Hello QEMU users.
I am interested in looking into a port for the Motorola Coldfire 5282. I saw
that others in the Coldfire family were supported, like the 5208 eval board and
the 5206 as a bare CPU. When I started looking into it I saw that several files
(e.g. coldfire/flexcan.h and coldfire/in
> On Sep 4, 2017, at 3:11 AM, Thomas Huth wrote:
>
> On 01.09.2017 21:03, William Mahoney wrote:
>> Hello QEMU users.
>>
>> I am interested in looking into a port for the Motorola Coldfire 5282. I saw
>> that others in the Coldfire family were supported, lik
> On Sep 5, 2017, at 4:37 PM, Peter Maydell wrote:
>
> On 5 September 2017 at 20:30, William Mahoney wrote:
>> Thanks Thomas. One more question. Somewhere there must be a "what
>> parts to look for where” document. You know, a “If you are interested
>> in the
rm)?
Or should I be installing Oxygen? :-)
On Sep 6, 2017, at 12:56 AM, Thomas Huth
mailto:h...@tuxfamily.org>> wrote:
On 06.09.2017 00:04, William Mahoney wrote:
On Sep 5, 2017, at 4:37 PM, Peter Maydell
mailto:peter.mayd...@linaro.org>> wrote:
On 5 September 2017 at 20:3
M, Peter Maydell wrote:
>
> On 8 September 2017 at 21:32, William Mahoney wrote:
>> "digic_load_rom()" knows the filename via an extern “bios_name” which is at
>> “include/sysemu/sysemu.h” but really lives in “vl.c”. It is set based on
>> “machine_ops” that com
> On Sep 13, 2017, at 3:34 AM, Thomas Huth wrote:
>
> On 12.09.2017 21:05, William Mahoney wrote:
>> OK a bit of an update and another question or two. First, you’re right, “it
>> just plain works”. What I’d like to verify today is that I am “doing the
>> right
what’s needed for, say, Linux?
> On Sep 13, 2017, at 2:02 PM, Laurent Vivier wrote:
>
> Le 13/09/2017 à 19:48, Thomas Huth a écrit :
>> On 13.09.2017 16:31, William Mahoney wrote:
>> [...]
>>> By the way, there is a link to a uClinux image on the emu documentation
&g
MU/qemu/scripts/tracetool/__init__.py",
line 224, in build
assert m is not None
AssertionError
I could start reading the python but I followed the documentation… Hm...
> On Sep 15, 2017, at 4:39 PM, Peter Maydell wrote:
>
> On 15 September 2017 at 21:41, William Mahoney wr
ood.
Bill
> On Oct 3, 2017, at 4:28 AM, Thomas Huth wrote:
>
> On 26.09.2017 23:12, William Mahoney wrote:
>> Thanks Peter!
>>
>> Couple of new things now that I had an afternoon to look again. I have
>> discovered that the eval board I can get my hands on
, Wireshark won’t let me cut/paste. But the ARP
is correct but the host is not answering it.
> On Oct 3, 2017, at 8:40 AM, Thomas Huth wrote:
>
> On 03.10.2017 15:21, William Mahoney wrote:
>> Hi Thomas;
>>
>> I was telling this to Peter as well offline. The initial pr
OK so really even though I see the driver sending the ARP requests, they’re not
actually ever making it to the host, even though the PCAP file shows them. In
other words, the PCAP file is "on the guest side" of the connection not "the
host side of the connection". Correct?
If that’s the case I
OK I took a look at slirp.c as you suggested.
I put in some fprintf’s in slip.c for the ARP requests and also in
arp_table_add and arp_table_search in arp_table.c. In the process I learned a
lot about how the ARP services work within QEMU and in the process also
realized what I was doing wrong.
Quick question. On the MCF5282 there is a huge memory mapped IO starting at
0x4000 and going for 1A. All of the IO is relative to this starting
point, so when my call back for an I/O write happens, for example, I get the
offset into the area. Fine.
In this area is the Fast Ethernet Con
> On Oct 25, 2017, at 1:37 AM, Peter Maydell wrote:
>
> On 24 October 2017 at 21:34, William Mahoney wrote:
>> Quick question. On the MCF5282 there is a huge memory mapped IO starting at
>> 0x4000 and going for 1A. All of the IO is relative to this starting
>
Thanks Peter - thoughts below.
> On Oct 25, 2017, at 9:51 AM, Peter Maydell wrote:
>
> On 25 October 2017 at 15:36, William Mahoney wrote:
>>
>>> On Oct 25, 2017, at 1:37 AM, Peter Maydell wrote:
>>>
>>> On 24 October 2017 at 21:34, William M
>>
>>> Related question. Where can I go look to get a better understanding of how
>>> the interrupts work? The supported 5208 has one PIC but the 5282 has two.
>>> In the 5208 code it uses sys bus_connect_irq() which references irqs[i].
>>> (Spell correcting made that array called “irks”!) Just
16 matches
Mail list logo
