Hi Kim,
I'm attaching four patches for you to test. They are to be applied on
top of the single-GPU-freq patch, but after additional testing I'll
push them to the main repo too.
First patch is pretty obvious and targets overall device stability
(marking yet another memory region as reserved).
Second and third patches ensure that the GPU GX domain is not toggled
too quickly (which can cause it to lock down), while the fourth patch
follows the vendor kernel and ensures that GFX3D is clocked during GPU
GX domain operations.
--
With best wishes
Dmitry
Hi Kim,
I checked, the OF overlap is harmless, as the Sighline hardware is not
using the SLPI DSP. Nevertheless here is the patch for your kernel
branch that fixes the overlap issue. I'll push it to our release branch
later today.
--
With best wishes
Dmitry
Hello Kim,
Could you please test the attached patch? With this in place I have been
running the 820 w/o any issues for the last week.
--
With best wishes
Dmitry
Hi Dmitry -
Just wanted to follow up on investigation of virtual channel support on our 4000-OEM product (snapdragon 820C) - would appreciate any information or ideas you can provide.
Do you guys have any experience with supporting multiple cameras over a single mipi channel?
Are there limitations? Sometimes I see that cameras must be the exact same resolution/frame rate and also frame synchronized?
Thanks for any ideas, Steve
Steve Sandven | Principal Software Engineer | SightLine Applications Inc. | Onboard Video Processing | he/him
503 880-6195 (mobile) | www.sightlineapplications.com<http://www.sightlineapplications.com/>
Hello,
In our last meeting on May 17 it was mentioned that there was work being done on the Lantronix device tree and it was booting in 6.4(? I think that was the version) kernel.
How's work on porting to 5.15 going? Is there a way to get the 6.4 kernel and the device tree to test out the booting locally for us?
Patrick Whewell
Software Engineer
He/him
patrick.whewell(a)sightlineapplications.com<mailto:patrick.whewell@sightlineapplications.com>
www.sightlineapplications.com<http://www.sightlineapplications.com/>
5711 S Hood Ave., Suite 100
Portland, OR 97239
[cid:image001.png@01D98EF0.EEFCA410]<http://sightlineapplications.com/>
Hi Dmitry,
On another 4000-OEM, I am running the latest 5.15 (with those 12 patches) and I am getting a hard crash on boot up. Attached is the dmesg log.
Thanks,
Kim
All,
Dmitry has now delivered what he believes to be the final set of updates to
Sightline in support of this project. Sightline is in the process of
testing these deliverables and we expect that the results will be at or
close to what was expected. If there are still gaps, we will of course work
to close them.
As of today, there are still 13.5 hours of Dmitry's time left available
under the most recent contract extension. This should provide adequate time
for any consultation needed and any updates and/or final tuning necessary.
I have attached a brief report on that burn to this email. Steve, I will
send you a more detailed version that you can share inside Sightline as
needed.
Please let me know if you have any questions or concerns.
While I will continue to be in touch as we close down the project, I want
to take this opportunity to thank everyone involved for all their work. I
am confident I speak for all of us at Linaro when I say I hope we have the
opportunity to work with Sightline Applications again in the future.
Kind regards,
Paul
--
[image: Linaro] <http://www.linaro.org/>
Paul Neuhardt | *Sr. Program Manager*
T: +44 0771 377 8664
paul.neuhardt(a)linaro.org <glen.valante(a)linaro.org>
IRC: pneuhardt
Hi Rhonda,
On 13/04/2023 02:01, Rhonda Cohen wrote:
> Hi Dmitry,
>
> Are you in contact with FedEx? I see that they have tried to deliver
> once, and then it was rerouted without success. Can you provide the
> address and telephone number you gave to FedEx? Perhaps, I can help
> close this.
Thank you. I have been pinging FedEx for the last several business days.
Today the locker company delivery timed out, so FedEx asked again how
I'd like to receive the parcel. I asked for delivery to the home address
again:
Piispanristi 2 A 86
02200 Espoo
My phone is +358469526397
However I do not think that additional intervention is required. Adding
additional information can mess things for them. It happened once already:
Krzysztof H (06/04/2023, 15:04:35): okay, as I see package was sent to
lockerbox at 2nd of April
Krzysztof H (06/04/2023, 15:04:46): to be honest it should be already in
lockerbox at 5th of April
Krzysztof H (06/04/2023, 15:04:58): you didn't recieved any sms with
location and code?
Me (06/04/2023, 15:05:11): No
Me (06/04/2023, 15:05:57): And the tracking page visible to me shows:
Me (06/04/2023, 15:05:58): Friday, 31/03/2023 Delay Rerouted to revised
delivery address
Krzysztof H (06/04/2023, 15:06:23): but rerouted wasn't possible due of
wrong phone number
Krzysztof H (06/04/2023, 15:06:33): correct phone number was provided
for us at 02.04
Me (06/04/2023, 15:07:39): Hmm. How is that possible? I had a missed
call and an SMS from FedEx on Friday, 31.03
Krzysztof H (06/04/2023, 15:07:44): I think sender made mistake, so they
send us correct phone number at the beginning of this week
Krzysztof H (06/04/2023, 15:08:18): becouse simply it depends on what
sender procided, in fedex system are two tabs for number, one at
package, second one is for notifications
Krzysztof H (06/04/2023, 15:08:29): I think sender just provided two
different numbers
Me (06/04/2023, 15:08:37): +358 469526397
Krzysztof H (06/04/2023, 15:08:44): that was phone number provided
firstly "5037249727"
Me (06/04/2023, 15:09:04): Yes. That is my phone and I was contacted on
this phone on Friday.
As you can see, the original phone was correct, then somebody
(Lantronix?) sent them another phone ("for notifications"), which
FedEx/lockers could not use to send me the additional info.
>
> Detailed Tracking (fedex.com)
> <https://www.fedex.com/fedextrack/?trknbr=521665246367&trkqual=2460019000~52…>
>
> Since the shipment has already passed customs, I am assuming that you no
> longer need the commercial invoice. It is attached in case you do.
I think I wrote in one of emails that Commercial invoice is required by
law. Customs can ask for one for the next 6 months.
>
> Best regards,
>
> **
>
> *Rhonda Cohen*
>
> she/her
>
> **
>
> +1 541-517-2768 mobile
>
> rhonda.cohen(a)sightlineapplications.com
> <mailto:rhonda.cohen@sightlineapplications.com>
>
> www.sightlineapplications.com <http://www.sightlineapplications.com/>
>
> <http://sightlineapplications.com/>
>
> *From:* Jordan Holt <jordan.holt(a)sightlineapplications.com
> <mailto:jordan.holt@sightlineapplications.com>>
> *Sent:* Friday, April 7, 2023 9:43 AM
> *To:* Rhonda Cohen <rhonda.cohen(a)sightlineapplications.com
> <mailto:rhonda.cohen@sightlineapplications.com>>; Steve Olson
> <steve.olson(a)sightlineapplications.com
> <mailto:steve.olson@sightlineapplications.com>>
> *Subject:* Fwd: [Sightlineapplications] Re: Low temperature GPU hang testing
>
> Forwarding to Rhonda
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> ------------------------------------------------------------------------
>
> *From:*Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org
> <mailto:dmitry.baryshkov@linaro.org>>
> *Sent:* Friday, April 7, 2023 6:02:33 AM
> *To:* Steve Olson <steve.olson(a)sightlineapplications.com
> <mailto:steve.olson@sightlineapplications.com>>
> *Cc:* Kim Steiner <kim.steiner(a)sightlineapplications.com
> <mailto:kim.steiner@sightlineapplications.com>>; Jordan Holt
> <jordan.holt(a)sightlineapplications.com
> <mailto:jordan.holt@sightlineapplications.com>>; Paul Neuhardt
> <paul.neuhardt(a)linaro.org <mailto:paul.neuhardt@linaro.org>>;
> sightlineapplications(a)lists.linaro.org
> <mailto:sightlineapplications@lists.linaro.org><sightlineapplications(a)lists.linaro.org <mailto:sightlineapplications@lists.linaro.org>>
> *Subject:* Re: [Sightlineapplications] Re: Low temperature GPU hang testing
>
> Hi Steve,
>
> On 07/04/2023 04:49, Steve Olson wrote:
> > Dmitry, did you get the board from lantronix yet?
>
> No, I did not receive it yet.
> Here is a transcript with the chat with support person:
>
> Krzysztof H (06/04/2023, 15:04:35): okay, as I see package was sent to
> lockerbox at 2nd of April
> Krzysztof H (06/04/2023, 15:04:46): to be honest it should be already in
> lockerbox at 5th of April
> Krzysztof H (06/04/2023, 15:04:58): you didn't recieved any sms with
> location and code?
> Me (06/04/2023, 15:05:11): No
> Me (06/04/2023, 15:05:57): And the tracking page visible to me shows:
> Me (06/04/2023, 15:05:58): Friday, 31/03/2023 Delay Rerouted to
> revised delivery address
> Krzysztof H (06/04/2023, 15:06:23): but rerouted wasn't possible due of
> wrong phone number
> Krzysztof H (06/04/2023, 15:06:33): correct phone number was provided
> for us at 02.04
> Me (06/04/2023, 15:07:39): Hmm. How is that possible? I had a missed
> call and an SMS from FedEx on Friday, 31.03
> Krzysztof H (06/04/2023, 15:07:44): I think sender made mistake, so they
> send us correct phone number at the beginning of this week
> Krzysztof H (06/04/2023, 15:08:18): becouse simply it depends on what
> sender procided, in fedex system are two tabs for number, one at
> package, second one is for notifications
> Krzysztof H (06/04/2023, 15:08:29): I think sender just provided two
> different numbers
> Me (06/04/2023, 15:08:37): +358 469526397
> Krzysztof H (06/04/2023, 15:08:44): that was phone number provided
> firstly "5037249727"
> Me (06/04/2023, 15:09:04): Yes. That is my phone and I was contacted on
> this phone on Friday.
> Me (06/04/2023, 15:09:32): ok. Anyway, how can we resolve this situation?
> Krzysztof H (06/04/2023, 15:10:51): well, I will ask our colleagues from
> support team to reach lockerbox company and to push your package. I will
> also tell them to send notification about location at this number +358
> 469526397, okay?
> Me (06/04/2023, 15:11:05): Yes, this is fine. Thank you
>
>
> >
> > Thanks,
> >
> > Steve
> >
> >> On Apr 6, 2023, at 11:54 AM, Dmitry Baryshkov
> <dmitry.baryshkov(a)linaro.org <mailto:dmitry.baryshkov@linaro.org>> wrote:
> >>
> >> On 06/04/2023 21:51, Kim Steiner wrote:
> >>> Hi Dmitry,
> >>> This is the parameter file from the board that is having issues.
> You can copy it to the /home/slroot/sl/bin folder on your 4000. It is a
> single cam0 configured as a testpattern 1080p image.
> >>
> >> Ack, thanks
> >>
> >>> Can you try the link again? I changed permissions.
> >>
> >> Yes, it works now.
> >>
> >>> Thanks,
> >>> Kim
> >>> -----Original Message-----
> >>> From: Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org
> <mailto:dmitry.baryshkov@linaro.org>>
> >>> Sent: Thursday, April 6, 2023 11:31 AM
> >>> To: Kim Steiner <kim.steiner(a)sightlineapplications.com
> <mailto:kim.steiner@sightlineapplications.com>>
> >>> Cc: Jordan Holt <jordan.holt(a)sightlineapplications.com
> <mailto:jordan.holt@sightlineapplications.com>>; Paul Neuhardt
> <paul.neuhardt(a)linaro.org <mailto:paul.neuhardt@linaro.org>>;
> sightlineapplications(a)lists.linaro.org
> <mailto:sightlineapplications@lists.linaro.org>
> >>> Subject: Re: Low temperature GPU hang testing
> >>>> On 06/04/2023 20:56, Kim Steiner wrote:
> >>>> Hi Dmitry,
> >>>>
> >>>> With the latest patch for 5.15, both boards that didn't boot up
> now boot, but one of the two boards crashes when we run our software.
> Attached is the dmesg log.
> >>> This is interesting. I also noticed the following:
> >>> [ 44.186437] qcom-camss a34000.camss: Failed to add VFE#0 to
> power domain
> >>> [ 44.186515] qcom-camss a34000.camss: Failed to power up
> pipeline: -22
> >>> [ 44.189179] qcom-camss a34000.camss: Failed to add VFE#0 to
> power domain
> >>> [ 44.199654] qcom-camss a34000.camss: Failed to power up
> pipeline: -22
> >>> So, some parts of the board might be underpowered.
> >>> I will take a look, what can be causing this issue or how can we
> cope with that. In the mean time, could you please describe, which
> camera is enabled on this board?
> >>>> With the latest patch for 5.15, we observe that the CPU functions
> (Analyze) is a little slower. We also observe that power usage has
> increased between 4.14 and 5.15:
> >>>>
> https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE
> <https://docs.google.com/document/d/1UD6FofrJKZ_9W7rGWTkN-DyoVI9KXQxktE>
> >>>> XY6eYpeUU/edit#bookmark=id.y65dtcn7w11x
> >>> I don't have access to this document.
> >>>>
> >>>> Thanks,
> >>>> Kim
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org
> <mailto:dmitry.baryshkov@linaro.org>>
> >>>> Sent: Wednesday, April 5, 2023 10:57 AM
> >>>> To: Kim Steiner <kim.steiner(a)sightlineapplications.com
> <mailto:kim.steiner@sightlineapplications.com>>
> >>>> Cc: Jordan Holt <jordan.holt(a)sightlineapplications.com
> <mailto:jordan.holt@sightlineapplications.com>>; Paul Neuhardt
> >>>> <paul.neuhardt(a)linaro.org <mailto:paul.neuhardt@linaro.org>>;
> sightlineapplications(a)lists.linaro.org
> <mailto:sightlineapplications@lists.linaro.org>
> >>>> Subject: Re: Low temperature GPU hang testing
> >>>>
> >>>> Hi Kim,
> >>>>
> >>>> On 05/04/2023 17:08, Kim Steiner wrote:
> >>>>> Hi Dmitry,
> >>>>>
> >>>>> This was two weeks ago when I ran this, but I do not think so.
> >>>>> Although we didn’t do any temp test in our freezer (room temp only),
> >>>>> because we didn’t hear back from you on if this was correct.
> Should we?
> >>>>>
> >>>>> I think you should create a single patch for us to test because the
> >>>>> last patch you sent us did not compile, so I’m wondering if the
> >>>>> correct patch was sent to us. In that patch, this line didn’t
> compile: dev_info(gpu:
> >>>>> "GPU setting to %ld\n", *freq);
> >>>>
> >>>> Please give a series of tests to the attached patch.
> >>>> I'm interested in:
> >>>> - speed bins for the boards that crashed when you tested the
> previous version, check the following line in the dmesg:
> >>>> [ 4.105174] adreno b00000.gpu: Detected speed bin 0
> >>>>
> >>>> - checking that GPU performance matches the expectations.
> >>>>
> >>>> - checking that the boards are stable in normal conditions and in
> the fridge test.
> >>>>
> >>>> Thank you for your testing!
> >>>>
> >>>> --
> >>>> With best wishes
> >>>> Dmitry
> >>> --
> >>> With best wishes
> >>> Dmitry
> >>
> >> --
> >> With best wishes
> >> Dmitry
> >>
> >> _______________________________________________
> >> Sightlineapplications mailing list --
> sightlineapplications(a)lists.linaro.org
> <mailto:sightlineapplications@lists.linaro.org>
> >> To unsubscribe send an email to
> sightlineapplications-leave(a)lists.linaro.org
> <mailto:sightlineapplications-leave@lists.linaro.org>
>
> --
> With best wishes
> Dmitry
>
--
With best wishes
Dmitry
Hello,
The package from Lantronix has arrived at the customs. Could you
please send me the corresponding invoice? I need it for customs
clearance. Thank you!
--
With best wishes
Dmitry
Hi Patrick,
On 21/03/2023 17:31, Patrick Whewell wrote:
> Hi Dmitry,
>
> I was looking for the device tree for the lantronix 5165 SOM and the schematics and attached are all of that.
>
> For the device tree I was trying to package up all of the individual includes, but it became too much so I decided to try and put it all in one file. To do this I used following commands:
>
>
> I preprocessed the dts file so that it would pull all the includes into one
>
> cpp -nostdinc -I ../../../../../../include -undef -x assembler-with-cpp qrb5165-iot-openq.dts > qrb5165-iot-openq.tmp.dts
>
> and then I tried to sort the file using the dtc
>
> dtc -I dts -O dts -o compiled.dts -s -@ qrb5165-iot-openq.tmp.dts
>
>
> Let me know if you would like it in a different format. I got some warnings while doing this, but no errors that I could see and the file looks like it should. Since it's such a large file (more than 3x as many lines as the upstream dts for qrb5165) it's sort of hard to make sure it's accurate.
>
> If you'd like any more schematics I can try to find more, but these should be what you were expecting.
Thank you, I will take a look.
>
> Patrick Whewell | Software Engineer | SightLine Applications, Inc | Onboard Video Processing
>
> -----Original Message-----
> From: Patrick Whewell
> Sent: Thursday, March 16, 2023 12:19 PM
> To: Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org>
> Subject: RE: Linaro kernel for QRB5165
>
> Hi Dmitry,
>
> Yes that is correct that we bought a board and sent it to you. I don't have any updates, but there isn't anything on our end that is holding up the delivery. I do want to mention that the higher priority is the work that you are doing for us with the Snapdragon 820c chip with the thermal GPU issue. And that anything with the 5165 should be second to that.
>
> In the coming days me and a co-worker here are going to try and get the Thundercomm board up and running with the Linaro kernel. Currently we are waiting for approval to access some documentation. We wanted to start with the Thundercomm instructions and then move to the Linaro stuff after using the board and making sure it all worked as expected. According to their README we need access to the MULTIDL_TOOL_USER_GUIDE. I only mention this because I wanted to provide context for the fact that I'm not in a rush.
>
> I will work on trying to get you access to the files that you mentioned. The device tree files have a lot of #include so I will track those down and try to package them up nicely for you and see if I can find the schematics. I appreciate all the information so far. It's pretty hard trying to find information on this type of stuff and I personally find it interesting so I'm excited to research more on some of these new things you mentioned.
>
> Patrick Whewell | Software Engineer | SightLine Applications, Inc | Onboard Video Processing
>
> -----Original Message-----
> From: Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org>
> Sent: Wednesday, March 15, 2023 1:22 PM
> To: Patrick Whewell <patrick.whewell(a)sightlineapplications.com>
> Subject: Re: Linaro kernel for QRB5165
>
> Hi Patrick,
>
> On Wed, 15 Mar 2023 at 19:17, Patrick Whewell <patrick.whewell(a)sightlineapplications.com> wrote:
>>
>> Thanks for that info! That explains why I couldn't figure out how it was selecting from the dtb appened to the kernel image. We'd like to eventually be able to use the Linaro kernel on the Lantronix board for testing. I can help supply some information but I believe it is supplying the vendor files.
>>
>> Lantronix provides a script that downloads and builds the kernel automatically but the relevant information is the following:
>>
>> In the repo manifest this is the information for the kernel:
>>
>> <remote fetch="https://source.codeaurora.org/" name="caf"
>> review="codeaurora.org"/> <default remote="caf"
>> revision="LU.UM.1.2.1.r1.3"/> <project groups="cyborg"
>> name="kernel/msm-4.19" path="src/kernel/msm-4.19"
>> revision="a103f94094dc38bc5931ca8559754e99558c0326"
>> upstream="LU.UM.1.2.1.r1.3"/>
>
> This is the public Qualcomm release of their 4.19 kernel
>
>> And the device tree that they use are located under:
>>
>> src/kernel/msm-4.19/arch/arm64/boot/dts/vendor/qcom/qrb5165-iot-openq.
>> dts
>
> And this is a proprietary device tree, written by Lantronix.
>
> I think Sightline has ordered a device kit, which should be delivered to me at some point. After I get it, I should be able to use its serial ID to get access to documentation and schematics of the board.
> Then we can port Linux kernel to their SoM/device kit. If you can provide SoM and base board schematics beforehand, it would speed up porting. Another option would be sharing the respective dts files to give us at least some kind of information regarding the board.
>
>> So I wouldn't be able to copy the needed files over and replace the device tree that is appeneded currently to the linaro kernel with the one from the Lantronix BSP? Our hope is to possibly get the linaro kernel running on the Lantronix board. If we want to do that, what would be some steps that we could take? We also purchased the Thundercomm platform so I can at least get that up and running but it'd be good to know why the Lantronix device tree wouldn't work with the kernel that is mentioned on the 96boards website.
>
> Thundercomm RB5 device is supported out of the box by the upstream kernel, see the qrb5165-rb5.dts file. Also you might be interested in the qrb5165-rb5-vision-mezzanine.dts which provides additional support for the cameras found on the Vision/Navigation mezzanine (included in the default RB5 kit). The former dts is available since 5.10, receiving incremental updates as the time goes. The later dts was merged into Linux 6.2.
>
> Unfortunately, you can not use device trees from Qualcomm releases with the upstream Linux kernel. Qualcomm writes them in a way that is not acceptable for the upstream kernels. Thus usually we have to repeat the porting up to some point.
> Basic steps to port Linux to the new Qualcomm-based board are the following:
> - Identify used PMICs.
> - Create the empty device tree including SoC and PMIC dtsi files.
> - Identify used UART and regulator tree. At this point the kernel should be bootable using debugging initramfs image.
> - Fill in the regulators description in the board dts
> - Identify storage options (eMMC, UFS, etc).
> - Identify used bus instances (I2C, SPI, corresponding QUPv3 wrappers, PCIe, USB)
> - Enable corresponding device nodes. Fill necessary supplies. Write corresponding pinctrl states.
> - Add support for the rest of necessary onboard devices, which can include sound codes, camera sensors, panel, DSI bridges/panels, etc.
> This might require writing additional drivers if the particular hardware piece is not supported.
>
>>
>> Thanks again!
>>
>> Patrick Whewell | Software Engineer | SightLine Applications, Inc |
>> Onboard Video Processing
>>
>> -----Original Message-----
>> From: Dmitry Baryshkov <dmitry.baryshkov(a)linaro.org>
>> Sent: Wednesday, March 15, 2023 2:40 AM
>> To: Patrick Whewell <patrick.whewell(a)sightlineapplications.com>
>> Subject: Re: Linaro kernel for QRB5165
>>
>> Hi Patrick
>>
>> On 14/03/2023 21:24, Patrick Whewell wrote:
>>> Hi Dmitry,
>>>
>>> I work over at Sightline Applications and I am working on the
>>> Lantronix SOM of the qrb5165. We had a meeting at the beginning of
>>> the month to talk about some additional help (on top of the
>>> snapdragon 820c work) regarding this kernel and it was mentioned
>>> that you were pretty familiar with the qrb5165.
>>>
>>> I recently was able to find out the device tree that Lantronix is
>>> using in their kernel and my hope was to copy over the files needed
>>> to the Linaro repo, build, and hopefully use fastboot boot to test it out.
>>>
>>> My question is that I notice the Linaro Kernel is building and then
>>> appending two separate .dtb files to the end of the kernel. I have
>>> previously worked on systems with u-boot where you select the
>>> fdt_file in the u-boot environment. How does this kernel/chip
>>> determine which device tree blob to use. I was thinking that it
>>> would just pick the first one appended but then it would be
>>> pointless to attach two separate blobs in that case.
>>
>> Yes, unfortunately Qualcomm adopted to use Android boot images and their own proprietary bootloader rather than using one of the standard ones.
>>
>> The bootloader looks for the 'best match' while looking for the DTB. To accomplish this, it uses DTB's qcom,msm-id, qcom-board-id and qcom,pmic-id to compute the dts 'score', then it uses the DTS with the best score. For example this allows Android team to bundle a single image with DTBs for both RB3 and RB5 boards, with the correct DTB being selected at runtime.
>>
>> In theory this should also allow you to use a single image for APQ8096 and QR5165 boards. However for the bringup I suggest ignoring that possibility and always using just a single DTB, suitable for your board.
>>
>> Note: I do not yet have access to Lantronix BSP. If it provides the vendor kernel (and thus vendor DTS), these files are not going to be compatible with the upstream kernel.
>>
>>>
>>> Thanks!
>>>
>>> *Patrick Whewell*
>>>
>>> *Software Engineer*
>>>
>>> He/him
>>>
>>> _patrick.whewell(a)sightlineapplications.com
>>> <mailto:patrick.whewell@sightlineapplications.com>_
>>>
>>> www.sightlineapplications.com
>>> <http://www.sightlineapplications.com/>
>>>
>>> /5711 S Hood Ave., Suite 100/
>>>
>>> /Portland, OR 97239/
>>>
>>> <http://sightlineapplications.com/>
>>>
>>
>> --
>> With best wishes
>> Dmitry
>>
>
>
> --
> With best wishes
> Dmitry
--
With best wishes
Dmitry
