Displaying 15 results from an estimated 15 matches for "achitectures".
Did you mean:
architectures
2007 Jul 25
1
Cricket
Hello
Has any one installed Cricket on Cenos ?
it seems there is a patch that should apply on Format.pm to specify
Achitecture,
but I can not find it .
Thanks
2013 Jun 05
2
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...4K.
Since each express device is behind such a port, this means
at most 15 such devices can use IO ports in a system.
That's why to make a pci express virtio device,
we must allow MMIO and/or some other communication
mechanism as the spec requires.
That's on x86.
Besides x86, there are achitectures where IO is unavailable or very slow.
> I don't think we should rush an ABI breakage if the only benefit is
> claiming spec compliance.
>
> Regards,
>
> Anthony Liguori
Why do you bring this up? No one advocates any ABI breakage,
I only suggest extensions.
> >
>...
2013 Jun 05
2
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...4K.
Since each express device is behind such a port, this means
at most 15 such devices can use IO ports in a system.
That's why to make a pci express virtio device,
we must allow MMIO and/or some other communication
mechanism as the spec requires.
That's on x86.
Besides x86, there are achitectures where IO is unavailable or very slow.
> I don't think we should rush an ABI breakage if the only benefit is
> claiming spec compliance.
>
> Regards,
>
> Anthony Liguori
Why do you bring this up? No one advocates any ABI breakage,
I only suggest extensions.
> >
>...
2013 Jun 05
2
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...It's not a device issue.
Anyway, let's put express aside.
It's easy to create non-working setups with pci, today:
- create 16 pci bridges
- put one virtio device behind each
boom
Try it.
I want to fix that.
> > That's on x86.
> >
> > Besides x86, there are achitectures where IO is unavailable or very slow.
> >
> >> I don't think we should rush an ABI breakage if the only benefit is
> >> claiming spec compliance.
> >>
> >> Regards,
> >>
> >> Anthony Liguori
> >
> > Why do you bring this...
2013 Jun 05
2
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...It's not a device issue.
Anyway, let's put express aside.
It's easy to create non-working setups with pci, today:
- create 16 pci bridges
- put one virtio device behind each
boom
Try it.
I want to fix that.
> > That's on x86.
> >
> > Besides x86, there are achitectures where IO is unavailable or very slow.
> >
> >> I don't think we should rush an ABI breakage if the only benefit is
> >> claiming spec compliance.
> >>
> >> Regards,
> >>
> >> Anthony Liguori
> >
> > Why do you bring this...
2004 Sep 02
0
Re: Alternative architecture CentOS 3 builds
Hey Nels,
I recently (within the last couple of days) updated
the FAQ with fresh, up-to-date information.
What achitectures are supported?
cAos x86 currently and x86_64 (AMD64) soon
CentOS-2 x86 only (sorry)
CentOS-3 x86 currently and x86_64 (AMD64) soon
Get it from the source here:
http://caosity.org/index.php?option=faq&task=viewfaq&artid=3&Itemid=5
I was told that AMD64 would be supported "so...
2010 Mar 18
0
Problem with forwarding: Now forwarding SIP/ XX to Local/
Hello,
here my achitecture:
client1--Asterisk1----ser1---centile
client2--
client1 do a call to centile.
centile do a forward to client2 (Diversion) and then use the same CALL-ID!
when asterisk1 receive the call with the same CALL-ID, it screen "Now
forwarding SIP/XXXX -000002f6 to 'Local/MCDU at kamailio ' (thanks to
SIP/YYY-000002f7)"
I don't want that asterisk receive
2013 Jun 05
0
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...s *breaks existing guests*.
Any time the programming interfaces changes on a PCI device, the
revision ID and/or device ID must change. The spec is very clear about
this.
We cannot disable the IO BAR without changing revision ID/device ID.
> That's on x86.
>
> Besides x86, there are achitectures where IO is unavailable or very slow.
>
>> I don't think we should rush an ABI breakage if the only benefit is
>> claiming spec compliance.
>>
>> Regards,
>>
>> Anthony Liguori
>
> Why do you bring this up? No one advocates any ABI breakage,
> I...
2013 Jun 05
0
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...t;
> It's easy to create non-working setups with pci, today:
>
> - create 16 pci bridges
> - put one virtio device behind each
>
> boom
>
> Try it.
>
> I want to fix that.
>
>
>> > That's on x86.
>> >
>> > Besides x86, there are achitectures where IO is unavailable or very slow.
>> >
>> >> I don't think we should rush an ABI breakage if the only benefit is
>> >> claiming spec compliance.
>> >>
>> >> Regards,
>> >>
>> >> Anthony Liguori
>> >...
2009 Jul 30
1
Migrate windows VM from i386 Host to x86_64 host
Somehow one of our Xen servers ended up loaded with the i686 xen kernel,
instead of the x86_64. The host has one windows VM running on it. The OS
partition is file-based, but it also has a logical volume partition
assigned for data. We would like to migrate the host server to a 64-bit
kernel, which means moving the VM to one of our other 64-bit host
servers. We tried simply copying the OS
2008 May 16
8
Patching Wine 1.0-rc1 with 3dmark.diff
Hey guys,
I'm a new Ubuntu convert (installed through Wubi, and am blown away!)
I'd love to get wine working so I play games etc, but I've got a lot of learning to do when it comes to installing and getting things working.
So, I want to use the 1.0-rc1 version of wine, but CoD4 requires the 3dmark.diff patch.
This is what I think I need to be doing:
with the 3dmark.diff file
2013 Jun 04
4
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Tue, Jun 04, 2013 at 03:01:50PM +0930, Rusty Russell wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
> > On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote:
> >> "Michael S. Tsirkin" <mst at redhat.com> writes:
> >> > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote:
> >> >> Rusty
2013 Jun 04
4
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Tue, Jun 04, 2013 at 03:01:50PM +0930, Rusty Russell wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
> > On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote:
> >> "Michael S. Tsirkin" <mst at redhat.com> writes:
> >> > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote:
> >> >> Rusty
2013 Jun 05
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...t; >
> > - create 16 pci bridges
> > - put one virtio device behind each
> >
> > boom
> >
> > Try it.
> >
> > I want to fix that.
> >
> >
> >> > That's on x86.
> >> >
> >> > Besides x86, there are achitectures where IO is unavailable or very slow.
> >> >
> >> >> I don't think we should rush an ABI breakage if the only benefit is
> >> >> claiming spec compliance.
> >> >>
> >> >> Regards,
> >> >>
> >> >...
2013 Jun 05
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...t; >
> > - create 16 pci bridges
> > - put one virtio device behind each
> >
> > boom
> >
> > Try it.
> >
> > I want to fix that.
> >
> >
> >> > That's on x86.
> >> >
> >> > Besides x86, there are achitectures where IO is unavailable or very slow.
> >> >
> >> >> I don't think we should rush an ABI breakage if the only benefit is
> >> >> claiming spec compliance.
> >> >>
> >> >> Regards,
> >> >>
> >> >...