similar to: [PATCH] xen/arm: Add EARLY_PRINT support for Broadcom brcm platform.

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE

George has release acked all of these. Otherwise mostly minor updates this time around. Summary: A == acked, M == modified A xen: arm64: Add 8250 earlyprintk support A xen: arm64: Add Basic Platform support for APM X-Gene Storm. A xen: arm64: Add APM implementor id to processor implementers. M xen: arm: add a quirk to handle platforms with unusual GIC layout A xen: arm: allow platform

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

These series patch enable Allwinner A31(code name sun6i) support in assemble. with these patches, the cpu 0 of sun6i SOC could successful boot into the c environment. Bamvor Jian Zhang (4): xen/arm: introduce Cortex-A7 support xen/arm: introduce Allwinner sun6i SOC basic support xen/arm: enable early printk for sun6i xen/arm: enable switch to hyper mode for sun6i xen/arch/arm/Rules.mk

I''m afraid this series is rather a grab bag and it is distressingly large at this stage. With this series I can boot an Xgene board until it fails to find its SATA controller. This is a dom0 issue for which patches are pending from APM (/me nudges Anup). As well as the APM specific platform stuff there are also some generic improvements which were either necessary or useful during this

Hi Ilia Thanks again for the reply. On Wed, 28 Oct 2020 at 14:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson > <dave.stevenson at raspberrypi.com> wrote: > > > > Hi Ilia > > > > Thanks for taking the time to reply. > > > > On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at

Hi Ilia Thanks for taking the time to reply. On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > The most common issue on arm is that the pci memory window is too narrow to allocate all the BARs. Can you see if there are messages in the kernel to that effect? All the BAR allocations seem to succeed except for the IO one. AIUI I/O is deprecated, but is it

Currently I am having 2 issues with my Avaya 4602 phone: First, the phone registers with my Asterisk server, but when I start dialing I get a busy signal after 4 digits. I specified in the dialplan on the phone to expect 10 digits and that solved that problem, but I still immediately get a busy after the 10th digit. The phone never sends a dial command to asterisk. Second, asterisk is

Hi Seeing as we (Raspberry Pi) have just launched the Compute Module 4 with an exposed PCIe x1 lane, people are asking about adding graphics cards. Seeing as you are the people who have the knowledge with regard to NVidia and nouveau, what are your immediate thoughts of nouveau working on ARM/ARM64? Is there a chance of this working? I'm no PCIe expert, although I can call on some expertise

Hello All, I am having an odd problem with Armin's chan-capi_cm on builds higher than 7955. It would seem that this happens on anything higher than 7955. What is happening is the isdn is ringing, then asterisk does a goto-if and just hangs. Asterisk itself is ok, but the isdn then rings out or busys out on the other side. Outgoing works fine, this only seems to effect incoming. I

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

I'm working on trying to get Samba 3.0.23c to work with Vista and I've run into a snag. If a share is set up for security = share, and protected with a password, when I try to mount the share using Start->Run->\\server\share, the password is rejected by Samba for about the first 10 seconds, but after that, it lets me in. I've tried all the common suggestions such as changing

Hi all, Im trying dial a user according to the device s/he uses. i mean if the user is using asterisk as a peer, then i have to pass the extension in the dial application like this: Dial(SIP/${EXTEN}@user) ;so that s/he can perform routing according to the DNID. and if the user is using sipura, linksys or grandstream i dial the user like this, Dial(SIP/user) so is there a way to know what kind

Hi, I've just (earlier today) updated from CVS so that I can apply the dtmf caller id patches. Unfortunately this has had an undesired effect. I have an intertex ix66 which up until the CVS update allowed me to register my * server with the ix66 for my local domain (eg sip.mydomain.com). Now it appears that asterisk gets totally confused and tries to register with itself! Anyone got any

Hello, This series has been split into two patches, one for arm and one for x86. I figured that this was easier than doing it as a single combined patch, especially as the changes are functionally independent. x86 has been boot tested, but arm has not even been compile tested as I lack a suitable cross compiler. However, the changes are just text replacement, so I dont expect any issues. The

We have a working PXE setup. I've tried to adapt it to UEFI as per RHEL6 manual, but the client won't boot. Strangely, tcpdump shows that the client tries to download all files via tftp from the dhcp server rather than the tftp server (they are different). next-server is pointing to the tftp server. Any clues?

On Tue, Nov 3, 2020 at 1:08 PM Dave Stevenson <dave.stevenson at raspberrypi.com> wrote: > > Hi Ilia > Thanks again for the reply. > > On Wed, 28 Oct 2020 at 14:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson > > <dave.stevenson at raspberrypi.com> wrote: > > > > > > Hi

On Wed, Oct 28, 2020 at 10:20 AM Dave Stevenson <dave.stevenson at raspberrypi.com> wrote: > > Hi Ilia > > Thanks for taking the time to reply. > > On Wed, 28 Oct 2020 at 14:10, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > The most common issue on arm is that the pci memory window is too narrow to allocate all the BARs. Can you see if there are

I am unable to get my 9133i to register with my asterisk server. I am including config files below, this a simple test network so there's nothing secret in the config files. I have upgraded the phone to the latest software version (1.4.3) I'm not sure what the problem is. I can call the phone from a softphone, but the 9133i says "no service" on the screen and I can't dial

Hi, I have a terminal adaptor connected to Asterisk. I found that when it connect to Asterisk v1.0.0,The TA send register msg, and get OK msg, but it get Notify msg every 1 minute, The TA reply with "call does not exist" , usually 10 minutes later, The TA is down. But it work well with Asterisk v1.0-RC1, only register and OK msg are sent and got, no Notify msg is sent to it.